Office 365 2010 Professional Plus and Terminal Servers (RDS Servers)

JeremyChapmanPassing on clarification from Microsoft’s Jeremy Chapman (pictured left) regarding Office 365’s Click-to-Run Office 2010 Professional Plus (available through “normal” subscriptions, such as the E3 plan as of this writing, April, 2015) and why it will not install on a RDS/TS Server:

“The Office 2010 subscription (365) install has activation based on retail activation, which is incompatible with RDS. RDS requires a Volume Activation package of Office 2010 – there is no way to make it work using the Office 2010 subscription package.

“The updated Office 365 ProPlus package has a new form of subscription retail activation (Shared Computer Activation), which works when installed on a server with the RDS role enabled. In that case, Office doesn’t activate in the traditional machine-level sense, but provides the logged in user-based temporary activation within that user’s profile. If the user has been provisioned for Office 365 ProPlus, they can log in with those credentials to unlock Office. In a VDI or hosted/remote app architecture, each user logging into the RDS host would need to be provisioned in Office 365 ProPlus to unlock Office for their session.”

A big thank you to Jeremy for clarifying the underlying reasons why 2010 does not work and 2013 does! Be sure to catch his great work over on the Office Blogs at http://blogs.office.com/author/jeremy-chapman too!

Posted in Uncategorized | Tagged , , , | Leave a comment

Tired of dealing with password resets

Issue Description

==============

Password Expiration Policy

 

 

Issue Resolution

==============

  1. Click Start > Search for Windows PowerShell > Right click ‘Run as administrator’.
  2. To establish connection, Open Windows Powershell (Run as administrator) then enter the Global Admin credential (Email address format) after running below script

 

$cred = Get-Credential

 

Set-ExecutionPolicy Unrestricted

 

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell -Credential $cred -Authentication Basic –AllowRedirection

 

Import-PSSession $Session

 

 

  1. Then we need to make sure we have Microsoft Online Module for Powershell already installed, in case if we don’t please download it from below source :

 

64 bit module version – http://go.microsoft.com/fwlink/p/?linkid=236297

                It may ask us to install the Microsoft Online Services Sign-In Assistant from below link : http://www.microsoft.com/en-us/download/details.aspx?id=39267

 

Then run the below commands and when asked enter the Global Administrator credentials again

 

Import-Module MSOnline

 

Connect-Msolservice

 

 

  1. To set the password policy to never expire, we may run the below commands
    1. For Individual user :-

Set-MsolUser –UserPrincipalName user@lmitc.com -PasswordNeverExpires $True

  1.  
    1. For All Users in the Organisation :-

Get-MsolUser | Set-MsolUser –PasswordNeverExpires $True

  1. To verify if password is set to never expire run the following command.

Get-MsolUser –UserPrincipalName user@lmitc.com | fl

See the below variable in the command shell ( PasswordNeverExpires :True )

 

  1. To set the password expiration to some number of days at domain level :
    Set-MsolPasswordPolicy -DomainName domain.com -NotificationDays 15 -ValidityPeriod 180

 

Note : Once we create a new user, we will have to set the password policy for that user again, as it is not possible to inherit that policy to the new user, so we will need to run the above commands again.

 

Posted in Uncategorized | Leave a comment

What does a fake voicemail virus email get you?

Well, for one example, here’s what Windows Defender Offline (http://windows.microsoft.com/en-US/windows/what-is-windows-defender-offline) found from a scan of an infected machine. Fortunately the user powered down the computer immediately after realizing he had been had.

Rogue:Win32/Winwebsec
Trojan
file:D:\ProgramData\hDa3n3aV\serv.bat
file:d:\users\–username-removed–\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Antivirus Security Pro\Antivirus Security Pro support.url
file:d:\users\–username-removed–\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Antivirus Security Pro\Antivirus Security Pro.url
folders:d:\users\–username-removed–\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Antivirus Security Pro\

TrojanDownloader:Win32/Kuluoz.D
containerfile:D:\Users\–username-removed–\Downloads\VoiceMail_Seattle_(206)4581802.zip
file:D:\Users\–username-removed–\AppData\Local\dqegmcmb.exe
file:d:\users\–username-removed–\AppData\Roaming\Microsoft\Windows\Recent\VoiceMail_Seattle_(206)4581802.lnk
file:d:\users\–username-removed–\Downloads\VoiceMail_Seattle_(206)4581802.zip->VoiceMail_Seattle_(206)4581802.exe
regkey:HKCU@S-1-5-21-3504191443-3983057376-3714753911-2621\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN\\ojphvgtg
runkey:HKCU@S-1-5-21-3504191443-3983057376-3714753911-2621\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\RUN\\ojphvgtg

A tip for you. After running the cleanup removal in Windows Defender Offline, reboot the machine with network disconnected to a Microsoft ERD Commander disc and use the registry editor and Windows Explorer to check the work of the cleanup tool and ensure everything is out of there. Then reboot and run Norton Power Eraser (https://security.symantec.com/nbrt/npe.aspx) for a final cleanup (has to be online for the Norton tool to work).

Posted in 4729 | Leave a comment

Need to pull data from your Exchange 2007 – 2013 logs?

Here’s how using PowerShell in the Exchange Management Shell:

get-messagetrackinglog -EventID “RECEIVE” -Start “10/22/2013 10:30:00 AM” -End “10/22/2013 4:00:00 PM” -ResultSize Unlimited |fl >c:\trackinglog.txt

By the way, the “-ResultSize Unlimited” will get you the full results to your text file and not truncate it.

Posted in 11361, 13090, 18152, 4885, Uncategorized | Leave a comment

Poor performance when you enable RemoteFX in Hyper-V on a Windows Server 2012-based computer that uses AMD processors

Working with Hyper-V on Windows Server 2012? Check out this KB article if you have AMD proc’s in your server(s) for a hotfix:

http://support.microsoft.com/kb/2770440/en-us?sd=rss&spid=16526

 

Posted in 12675, 15587, 15589, 17621, 17622 | Leave a comment

Windows 8 Mail requires 3rd party SSL certificate for Exchange

If you have a Windows 8 Mail client that won’t connect to an Exchange account, check to see if you have a self-assigned SSL certificate installed on your Exchange Server. A “3rd party” certificate (GeoTrust, Thawte, VeriSign, Go Daddy for example) will take care of your problem. You can confirm if this is in fact the case by running the Microsoft Remote Connectivity Analyzer, testing Exchange ActiveSync (https://www.testexchangeconnectivity.com/).

Posted in 12406, 17239, 3202 | Leave a comment

No PSSBS Meeting for November, 2012

For those who are not members of the PSSBS Yahoo Group, or in case you haven’t seen the announcement in our PSSBS Yahoo Group, there is NO NOVEMBER MEETING. I am in Las Colinas, Texas at an MVP “Deep Dive” in Server 2012 Essentials and Multipoint. We will be meeting in December, with a presentation by CRU-DataPort.

Posted in 2828 | Leave a comment

Install Exchange 2010 in two (2) steps

At SMB Nation 2012 in Las Vegas, I have been asked multiple times for the URL to the TechNet Article that has the simple steps to install Exchange Server 2010 on a member server in a Windows Server 2012 Essentials network. You can find it at http://technet.microsoft.com/en-us/library/aa997281.aspx.

Steps below from the comments at the bottom of the TechNet page:

How to install Exchange 2010 in two steps!
The following comments are from Michael Smith, Exchange MVP, and posted here with his permission. – Steve

In general, I ignore the wizards when installing Exchange. It’s literally easier (IMHO) to install from the command line. And it takes only two steps.

1. In an elevated cmd prompt, install the Exchange prerequisites and reboot:
sc.exe config NetTcpPortSharing start= auto
REM cd into the ‘Scripts’ directory in the Exchange installation folder/media
cd /d c:\Ex2010SP2\Scripts
ServerManagerCmd.exe -ip Exchange-Typical.xml -Restart

 
(You’ll get a warning about ServerManagerCmd being old-fashioned. Ignore it.)

2. After the reboot, in an elevated cmd prompt, install Exchange:
setup /r:mb,ca,ht /on:”First Organization”

That’s it.

How do you use this with Windows Server Essentials 2012?

1. Purchase Windows Server 2012 Standard (Volume Licensing is your best bet in order to get the required Essentials keys for installation).
2. Install as parent Hyper-V OS. Windows Server 2012 provides 1+2 licensing. (http://download.microsoft.com/documents/uk/SMB/products/windows-server/WS2012_Licensing-Pricing_Customer_FAQ.pdf)
3. Install Windows Server 2012 Essentials (Download the trial available at http://www.microsoft.com/click/services/Redirect2.ashx?CR_CC=200142594 to get the bits) as your first child virtual machine. You will need an Essentials key for this at install. You are exercising your downgrade rights of Windows Server 2012 Standard in this process.
4.

Posted in Uncategorized | Leave a comment

Exchange 2007 updates week of 10/7/2012 – Exchange down on reboot.

Small Business Server 2008 (Exchange 2007) updates from this past week’s patch Tuesday are causing an interaction that is causing Microsoft Exchange System Attendant and Microsoft Exchange Information Store to not fire up. Hearing that two reboots may get you there. You can also fire them up manually in the Services MMC.

If you see the Microsoft Exchange System Attendant “starting,” then you’ll need to kill the mad.exe process from the Task Manager in order to get the services to start.

Posted in 11361, 8634 | Leave a comment

Looking for Server 2003 and XP files you can remove / delete from the C drive?

If you have aging Windows XP and Windows Server 2003 machines that have filled up their C: drives, here’s a Microsoft KB with documented safe files you can remove:

KB 956324 – How to reclaim disk space on Windows XP and Windows Server 2003-based computers.

http://support.microsoft.com/kb/956324

To cut to the chase on which Windows Update files you can delete (there are other directions in the KB as well, but these are what most server admins will be looking for) are below (taken from the KB as of 9/4/2012):

Delete Windows update files

Warning If you delete the folder for each update, the corresponding Windows update cannot be uninstalled. Consider the effect that this will have on the computer before you delete the Windows update files.

To delete Windows update files, follow these steps:

  1. Delete only those %Windir%/$NtUninstallKB number$ folders that were created more than a month ago as backup files for Windows updates. Do not delete those that were created within the last 30 days.
  2. To delete the download cache for Windows updates, delete all the folders in the %Windir%\SoftwareDistribution\download folder that were created more than 10 days ago.
  3. Delete the following log files in the %Windir% folder:
    • kb*.log
    • setup*.log
    • setup*.old
    • setuplog.txt
    • winnt32.log
    • set*.tmp

Delete Windows XP service pack files

Warning If you delete the backup folders for each Windows XP service pack, you will be unable to uninstall Windows XP service packs.

If you delete the folder for the installation files and the cache for the Windows XP service pack, you will be unable to restore corrupted Windows XP service pack files or to install additional Windows XP features that are not installed by default. You may want to keep a copy of these files in another location. For more information about how to keep a copy of these files, click the following article number to view the article in the Microsoft Knowledge Base:

271484

Files and folders are added to your system after service pack is installed

Consider the effect that this will have on your computer before you delete these files.

To delete Windows XP service pack files, follow these steps:

  1. Delete the %Windir%\$NtServicePackUninstall$ folder to delete the backup folders for the Windows XP service packs.
  2. Delete the %Windir%\ServicePackFiles folder to delete installation files and cache folders for the Windows XP service packs.
Posted in 17260, 17261, 2738 | Leave a comment