Google Cloud Directory Sync: Error while creating user due to address collision


“Error while creating user due to address collision (either an excluded resource has this address, or a change was made outside of GCDS and the cache is stale).” This would happen daily and both to staff and student accounts.

Status: Known issue in Google Cloud Directory Sync 4.4.26 but due to the drastic changes in this version rolling back is not recommended.

According to support, this is a known issue in Google Cloud Directory Sync 4.4.26 but due to the drastic changes in this version rolling back is not recommended.

Work Around:  This argument added to the command line flushes the cache:


“C:\Program Files\Google Cloud Directory Sync\sync-cmd.exe”


-a -f -c C:\Users\user\yourconfigurationfile.xml

The -f argument is listed in the documentation as ‘resolves specific troubleshooting issues’ but it flushes the cache.

To confirm clearing the cache resolved the issue support had me locate the GADS_nonAddressPrimaryKeyFile.tsv in C:\Users\USER_GADS and rename it to GADS_nonAddressPrimaryKeyFile_Old.tsv. The path to the file is located in the .xml file:


The .tsv file holds a primary key for all the users. Renaming it causes GCDS to take alot longer as it recreates all the primary keys. The primary key is used as a unique identifier for name changes.

I hope this helps if you run into it!


Data was dropped due to too much outstanding data in rule “Microsoft.SystemCenter.Agent.MaintenanceMode” running for instance “site-scom.local” with id: in management group “Your Management Group.”

Resolve: If in a single management server environment, take the management server out of maintenance mode.

Never put a management server in maintenance mode:

I am new to SCOM and recently started using ‘maintenance modes’ based on the following article:

My logic while flawed was to put the server in maintenance mode after applying updates and reboot. I left it in maintenance mode to resolve a couple of start up errors but all monitoring ceased. Take the server out of maintenance mode…and all was well…humbling… easy fix.

How to create UEFI bootable USB Media to install Windows Server 2016

It is a long story on why I had to use a USB drive to build a server but if you ever find yourself in that position, this was a great article:

How to create UEFI bootable USB media to install Windows Server 2016

Thanks @p0w3rsh3ll. You are part of a brilliant PowerShell community out there.


Autodesk installation through SCCM 2012 1606 (avoiding Manifest Error 0x80004005)


I had success with:(Maya 2017 (3GB), Inventor 2017 (12GB), even Building Design Suite 2017 (18GB) as an application using “.\Img\Setup.exe /W /q /I Img\MAYA_2017.ini /language en-us” but the Entertainment Creation Suite Ultimate (6GB) would fail. That (my understanding) is due to the number of files in those installations and not the size of the installations. I like using applications versus packages because of the requirements and detection methods. So to make it work I created a self extracting archive or a script to zip, copy, and install (credit to the authors below)

cmd C:\PDSU_2017
xcopy PDSU_2017.7z C:\PDSU_2017 /s
7za x C:\PDSU_2017\PDSU_2017.7z
“.\PDSU_2017\Img\Setup.exe” /W /q /I PDSU_2017\Img\PDSU_2017.ini /language en-us
rmdir C:\PDSU_2017 /q /s

Your source directory will have three files, 7za, PDSU_2017.7z (archive of installation files), and PDSU_2017.cmd (the above script). It worked great and I can now move on. 🙂


Detection method:

I look to the registry on a remote computer for the product under the uninstall key. For the Production Design Suite Ultimate I chose Mechanical value ‘AdskPackageName’.


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AutoCAD Mechanical 2017 – English

Set your client cache:



How to add an application:


How to deploy a scripted application installation with SCCM 2012


SCCM 1606 Backup and restore to new hardware

Hey all,

Here was my experience on performing a migration of an SCCM primary site server for version 1606. Credit goes to the SCCM community out there…such a great resource.

Scenario: Primary Site Server with 26 distribution points

First get the prerequisites in order:

  • Windows ADK
    • Deployment Tools
    • Windows Preinstallation Environment (Windows PE)
    • User State Migration Tools (USMT)
  • IIS @prajwaldesai has great notes on what is required and
  • Install SQL (Verify your SQL version)
    • SQL Server Feature Installation
    • Database Engine Services
    • Reporting Services – Native
    • Feature Directories (Default)
    • SQL Server Agent, Server Database Engine, Server Reporting Services
    • Windows Authentication Mode – Enterprise Admins
  • Backup Site Maintenance Task (Wonderful! Installation Media Everything! So awesome)

@anoopmannur ‘s article was the route I followed with these additions:

2. robocopy /source /destination /mir

For example robocopy \\train-sccm-dp.train.local \\train-file.train.local /mir


The restoration was easy but there were a few things that I overlooked. The WSUS server on the previous server was 10.0 GB and I didn’t make any effort to back it up prior so I setup WSUS up again. Also be sure to check the group memberships of your primary site server.

The below article from SystemCenter Dudes was super helpful but the part I didn’t understand was when the database was actually created. The step when the SUSDB is created (only post installation task to run):


That was it! The 1606 restore process was done. My struggles were with the below and that did take some research to figure out but hopefully I won’t be doing this for a while. 🙂


Slow Console performance while working with applications and deployments.

Resolve:  We increased SQL memory usage from 8GB to 24GB and it made alot of difference.


Failed to get RDC signature path for package 00100150 version 2. Error = 2 SMS_DISTRIBUTION_MANAGER 10/25/2016 3:40:09 PM 6260 (0x1874)

Resolve: Restart the distribution points and redistribute Content to DPs

Error: Software Update Point 

PublishApplication(9380D44D-DA80-48C3-97DE-C9C528F73A2D) failed with error System.InvalidOperationException: Publishing operation failed because the console and remote server versions~~do not match.~~   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~   at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String sdpFile)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile)

Resolve: Make sure the WSUS server service on your Software Update Point is running. Through the process, it was in a disabled state and took a bit (and talking with a friend) to find that (doh!).

Error: Trying to download apps from the application catalog but stuck at 0%:

Successfully queued event on HTTP/HTTPS failure for server ‘sccm-dp.train.local’                                                                                                 Error sending DAV request. HTTP code 500, status ‘Internal Server Error’   Error retrieving manifest (0x87d0027e).  Will attempt retry 1 in 30 seconds.                                                                   CContentDefinition::TotalFileSizes failed; 0x80070003

Resolve: Import HTTPS certs again for distribution points (password protected)


Inventory Data Loader failed to process the file C:\Program Files\Microsoft Configuration Manager\inboxes\auth\\Process\HPP1QPNF.MIF because it is larger than the defined maximum allowable size of 5000000

Resolve: Adjust Max MIF size here: HKLM\Software\Microsoft\SMS\Components\SMS_INVENTORY_DATA_LOADER\Max MIF Size

Great articles that helped me through this process:

How to install Software Update Point in SCCM 2012 R2

SCCM 2012 R2 Step by Step Guide

How to Migrate SCCM CB 1606 Primary server to new hardware or new virtual server

How To Deploy Software Updates Using SCCM 2012 R2


WinPE reboot after ‘preparing networking’ (SCCM )

There are a few articles out there regarding reboots after preparing network connections and to add to the list make sure all your content is available. I had the following error:

Content location request for ApplicationModel:ScopeId_1191231226-842B-405D-9185-DC12334d8F0E4/Application_ce9023ad6-fe02-4598-8b35-8de634adassb6b:1 failed. (Code 0x80040102)

I copied (net use & xcopy) the log from c:\smsts\smsts.log to my local hard disk and opened it with cmtrace.exe (Site Server \SMS_001\tools). I then went to my SCCM console -> Software Library -> Task Sequences (choose the TS you are working with)-> References ->  and selected the object ID column to see what Application that was referring to. In the case it was Google Chrome. I needed an upgrade version anyways so after adding the newest version all was well.



Location of SMSTS log during SCCM OSD

Canon ImageRUNNER 3235 Scanning to Windows 2012 R2

I ran into this after KB3161949 was applied to a file server. The above ImageRunner uses NETBIOS over SMB and the security update hardens that. Without being able to upgrade to a new Copier we decided to remove the security update.


More Info:

STMP Relay, Office 365, & Shoretel

Hi! Everyone,

I wanted to share with you my journey to setup an smtp relay server (copiers, fax, voice mail notifications, etc. ) and what I finally found that made it work:

If you are using a Shoretel system make sure that you have notificaitons on, a valid email, and the SMTP relay server set (Sites -> HQ -> SMTP Relay)



You will also want to follow step three to install IIS on a server:

You can follow through that entire article if you need to send to domains that you don’t have authoritative control over.

Once IIS is setup right click on the default SMTP virtual server and make sure that authentication is set to anonymous and relay has the devices you want to to be able to send mail.


Make sure you adjust the limit size for larger attachments, a fax might exceed this limit of 10MB.


Set Outbound Security as pictured below, Outbound Connections to TCP Port:25, and the smart host to be where your mx records are pointed to. This is usually You will also find alot of references to or These might also be valid choices for you.


Add a remote domain with your domain name and finish.


Under the properties of the domain now listed choose ‘Allow incoming mail to be relayed to this domain’ and ‘forward all mail to smart host’. This value will be the same as the smart host you listed above.

You can see mail go into the queue here and then disappear. If it stays there you have a problem:


Easy tool to test whether relay is working:

Additional Resources: