Kevin Oppihle's Tech Notes

Problem : After you install the Windows Management Framework 4.0 which includes the update to Powershell 4. It installs successfully but Powershell 4 is missing? Solution : You probably did not installed the pre-requisite .net 4.5 http://www.microsoft.com/en-us/download/confirmation.aspx?id=30653   Install .net 4.5 on 2012 from the built in installer. On Windows 7 or 2008 R2 use the download link above. Note: 2008 R2 SP1 also is required Once .net 4.5 is installed then rerun the installer for Windows Management Framework 4.0 http://www.microsoft.com/en-us/download/details.aspx?id=40855 Note: you do not have to uninstall and reinstall the package just rerun it. Restart the system and confirm the version of Powershell you have running use the following command within powershell: $PSVersionTable.PSVersion Note: For other version prerequisites see the link below for more details Credit- http://social.technet.microsoft.com/wiki/contents/articles/21016.how-to-install-windows-po

Warning: Uninstall all previous versions of office, that includes 2013 and 365 demos before proceeding Users must be admins on their systems temporarily for the GPO to work. Create a shared folder on your central server for example \\SRV-UTIL01\OfficeDeploy\ Download the Office Deployment Tool and extract to \\SRV-UTIL01\OfficeDeploy\ http://www.microsoft.com/en-us/download/details.aspx?id=36778 Create 2 XML files with the options The first is Download.XML which sets your path, 32 or 64 bit, and is used for the download process: <Configuration> <Add SourcePath="\\SRV-UTIL01\OfficeDeploy\" OfficeClientEdition="64" > <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> </Product> </Add> </Configuration> The second is RDPConfiguration.xml used to deploy Office 365 ProPlus package Note: The example that is included with the Office Deployment Tool might as well be blank since it is rem’d out with t

Caution : DO NOT run this on Domain Controller C:\ and only run on roaming profiles folders, or my docs shares day of migration to avoid ownership change issues. Confirm Domain trust is in place and users and groups have been migrated Test ping of olddomain.org from new domain Test ping of newdomain.org from olddomain Add newdomain.org domain controller host records to olddomain.org including reverse DNS records Confirm the user running the app is a domain admin in BOTH domains Download SubinACL here: http://www.microsoft.com/en-us/download/details.aspx?id=23510 /Migratetodomain- command will add the permissions of the new user to the old files and folders for example if jimbob@olddomain.org was migrated to the new domain jimbob@newdomain.org and you run the command below any file or folder in that path that has jimbob@olddomain.org will add Jimbob@newdomain.org with the exact same permissions. This is a safer way to migrate by keeping the old and new permissions intact while a

Log onto Microsoft Volume License site: https://www.microsoft.com/Licensing/servicecenter/default.aspx At the top of Home select “View Online Service Activations” as shown below Select the license and click Manage Activations as shown below: It is assumed you already have 365 admin account setup so select “I have and account for my organization to use” as shown below: Enter in your 365 Admin account credentials and Sign in: Select which licenses you wish to activate and select Start Activation. Note: You do not have to active them at the same time as in the case above they waited 2 months to activate the E3’s but immediately activated the E4’s. The License Key will be displayed. Select Next: Final Confirmation! And Activate!: Confirm Activation in your 365 console under Billing and Subscriptions :

Log onto the Licensing Management Platform using the following link: https://licensingplatform.trendmicro.com/xLP/EndUserMng/EndUser/Landing?T=4DBC6EAD Top Right Select “Trend Micro Remote Manager”: Left side “Customers”: Select that specific Customer and “WFBS-SVC_WFBS_SaaS_MSP” Select Administration> Manage Co-Administrators: Add administrator: Enter in the username, information, submit and it will send out an email for their approval and allow them to set their own password: Note: They are a FULL administrator at this point so be very cautious and warn them of potential dangers/impact to making any changes.

$UserCredential = Get-Credential Enter in 365 admin and credentials when prompted : $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic –AllowRedirection Import-PSSession $Session Connect-msolservice Enter in 365 admin and credentials when prompted : Username change: Set-MsolUserPrincipalName -newuserprincipalname newname@yourdomain.com -userprincipalname oldname@yourdomain.com Credit- https://technet.microsoft.com/en-us/library/hh974317.aspx

So a client had an old SBS 2011 server that was out of service with Exchange 2010 on it. They have been running Office 365 for about 9 months and did a clean cutover no migration, since most of the data was, as they put it “old junk”. However they wanted a copy of that “old junk” before that server is taken to the recycle center just in case. Which is always a good idea and sounds simple enough. Since it is exchange 2010 you don’t have to use exmerge or some other older tool you can use powershell commands that export each mailbox to its own big .PST to a drive share that will be copied to a copy external hard drives or tapes and put on a shelf and be forgotten about till some needs a drive or tape. So I start out trying to run the basic command to give myself permissions: New-Managementroleassignment –Role “Mailbox Import Export” –User “Administrator” Command does not exist … (Quick Research and I need to add Exchange Service Pack 1) Install SP1 and run the command above again and i