Kevin Oppihle's Tech Notes

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 Configuration.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 th...

Log onto the Server as an Administrator 1. open Ntdsutil 2. set dsrm password . 3. reset password on server null . 4. Type the new password when you are prompted and enter 5. Reenter the new password and enter 6. Q to quit 7. Document the change

You setup your new domain imported or added user then realize you left out a field such as mail details. Since all users are different you can’t do a bulk select all and edit you have to set each one individually or via a .csv file and script. Here is a working example: note : If your “user logon name” does not match your “user logon name (Pre-Windows 2000)” it will fail on those users. Create an excel file with the following fields and export to a csv called c:\admailfield.csv name mail kevin.oppihle kevin.oppihle@domainname.com Create a .txt file and input the following $users=import-csv C:\Source\admailfield.csv foreach($user in $users){ $u = Get-ADUser $user.name -Properties mail $u.mail = $user.mail  Set-ADUser -instance $u } Save the file as admailfiled.ps1 Open powershell as an administrator on you local AD server and run   ./admailfield.ps1 You can then use AD users and computers to confirm the changes were added to AD Credit References : DuRand Brya...

You setup Office 365 DirSync and the default domain for the users is domainname.onmicrosoft.com instead of your default defined domain in Office 365. It will not allow even the Office 365 administrator change the email addresses of individual users from the Office 365 console. The reason is with AD synchronization enabled by default it uses the proxy address field of the user sent from AD. If that is blank in AD it will use domainname.onmicrosoft.com. You can either use ADSIedit to modify the proxy address fields individually for each user or you can use a powershell script and csv file such as the one below to do so in bulk. Word of warning it will overwrite any existing proxyaddresses not just SMTP: (primary) it will also remove smtp: (aliases) if you run it as is. Additionally if your “user logon name” does not match your “user logon name (Pre-Windows 2000)” it will fail on those. Create an excel file with the following fields and export to a csv called c:\mailboxlist.csv na...

If you do directory sync from AD to Office 365 users will not be able to change their passwords on the Office 365 portal. Since the AD sync is a one way process the password changes do not come back into AD locally. Thus by default the Office 365 Portal will not allow users to change their passwords as they will just be overwritten by the local AD. The problem this creates is sometimes you have a mix of users some local and some that may not have local domain access to change their passwords. The following is a work around using OU exclusion from DirSync. First we need to put the users in a separate OU such as “Webmail” then we will exclude that OU from DirSync. That will allow them to change from “Directory Synced” to “Cloud”. Which you can confirm in the Office 365 Admin Console. Here are the steps: Caution : Seasoned Domain Admins Only this is Active Directory and email flow will be impacted for users as they are changed “you break it you bought it…” Copy Shortcut to desktop C:\Pr...

If you do directory sync from AD to Office 365 you may not want to replicate all users and groups in your full AD structure which is what is replicated by default. You can exclude or specify which OU’s to synchronize using the following instructions. Caution : Seasoned Domain Admins Only “you break it you bought it…” Create the following shortcut to the desktop C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\miisclient.exe Open and select Management Agents and The Active Directory Connection: Right Click and Select Properties: Select Configure Directory Partitions and Containers: You will be prompted for credentials enter in your LOCAL ADSync Username and Password: Browse and Include or Exclude the OU’s as necessary: Select “OK” “OK” You can now force the DirSync process. Open up PowerShell as Administrator and Run the following command to initiate a sync: Import-Module DirSync Start-OnlineCoexistenceSync -fullsync Sele...

https://filezilla-project.org/download.php?type=server Install using defaults then start customizing: Internal IP Address: You can specify what IP’s are blocked or allowed: Use a custom port range so you can specify the range in firewall and the external IP: Review buffer settings: Specify admin interface port: Configure logging: Set any speed limits: Generate a new Certificate and point Private Key and Certificate file to the same certificate.crt: Note: external certificates would not work properly even with format changes Enable automatic bans and customize settings as necessary: Configure your External Firewall to port forward and allow traffic: Configure the Firewall Inbound and Outbound Rules on the FileZilla Server: Name rules SFTP IN and SFTP OUT:   Ports 21,22,990 and the port range specified earlier: Setup the users and groups: Setup shared folders: Now you are ready to test