Came across an issue with the Configuration Manager Console crashing when adding boundary groups to a distribution point.  When going into properties of a distribution point on the boundary groups tab and clicking Add I would recieve this error:





A lot of business talk lately has been that Citrix is working with Goldman Sachs to seek a buyer.  Citrix is currently valued at around 13.3 Billion with the stock having rose 30% over the past 12 months. 



It is recommended for Administrators to send out a company email to warn about a large increase in W-2 phishing attacks going on.  The FBI and IRS have released several warnings that this has seen a significant increase this year.


In this blog, we will migrate on-prem home drives located on a file server into Microsoft OneDrive for Business.  The Home drives are all on a file share in one location.  We will run a PowerShell script to extract the folder names which will also be used to map the OneDrive user accounts.  To do the final migration we will leverage the ShareGate tool.  More and more companies are leveraging the cloud for home drives as it can be accessed from any device and eliminate the need for a VPN or Direct Access.  Many companies also already have access to OneDrive for Business with their Office 365 license and can take advantage of this to retire file servers and free up space.


Noticed on Windows Server 2012 R2 the following event ID 1202 which keeps showing up every ~30 minutes when Group Policy updates. 

Event ID: 1202

Source: SceCli

Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.

Advanced help for this problem is available on Query for "troubleshooting 1202 events".

Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID.  This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO.  To resolve this event, contact an administrator in the domain to perform the following actions:

1.             Identify accounts that could not be resolved to a SID:

From the command prompt, type: FIND /I "Cannot find"  %SYSTEMROOT%\Security\Logs\winlogon.log

The string following "Cannot find" in the FIND output identifies the problem account names.

Example: Cannot find JohnDough.