Home
%3CLINGO-SUB%20id%3D%22lingo-sub-737137%22%20slang%3D%22en-US%22%3EResolved%3A%20Known%20issue%20for%20Windows%2010%201809%20when%20using%20Account%20CSP%20for%20renaming%20devices%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-737137%22%20slang%3D%22en-US%22%3E%3CP%3E%3CEM%3EUpdated%2012%2F19%2F19%20-%26nbsp%3BThe%20fix%20for%20this%20issue%20has%20been%20released%20with%20the%208C%20(Third%20week%20of%20August%202019)%20Windows%20Update%2C%20which%20is%20the%203rd%20week%20of%20August%20(See%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FWindows-IT-Pro-Blog%2FWindows-10-update-servicing-cadence%2Fba-p%2F222376%22%20target%3D%22_self%22%3EWindows%2010%20update%20servicing%20cadence%3C%2FA%3E).%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3ENote%3A%20Any%26nbsp%3Bdevice%20that%20has%201809%2C%20but%20doesn%E2%80%99t%20have%20the%20August%20update%20will%20have%20this%20issue.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20enrolling%20devices%20through%20Autopilot%2C%20you%20can%20%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fdocs.microsoft.com%252Fen-us%252Fintune%252Fenrollment-autopilot%2523create-an-autopilot-deployment-profile%26amp%3Bdata%3D04%257C01%257CHimali.Pethe%2540microsoft.com%257C79611ee2810a4045b6d308d6fa5889b7%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636971655508618317%257CUnknown%257CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%253D%257C-1%26amp%3Bsdata%3DzkDl5ObIE4XZJlfIyHgEMTes6i74wBuXRoqE3SuhCPg%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ecreate%20an%20Autopilot%20deployment%20profile%3C%2FA%3E%20and%20configure%20the%20%E2%80%9CApply%20device%20name%20template%E2%80%9D%20setting%20to%20create%20a%20device%20name%20for%20Windows%2010%201809%20and%20higher%20devices%20at%20initial%20startup.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F122113iF8D6BA4793E13458%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Spencer%20account%20CSP%20post.jpg%22%20title%3D%22Spencer%20account%20CSP%20post.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%E2%80%99ve%20discovered%20a%20bug%20in%20this%20setting%20with%20%3CSTRONG%3EWindows%2010%201809%3C%2FSTRONG%3E%20where%20using%20a%20prefix%20with%20the%20%25RAND%3Ax%25%20macro%20does%20not%20work%20to%20apply%20a%20device%20name%2C%20if%20the%20total%20of%20the%20prefix%20and%20macro%20adds%20up%20to%2015%20or%20more%20characters.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20a%20workaround%20you%20should%20ensure%20that%20you%20enter%2014%20characters%20or%20less%20overall%20when%20using%20device%20name%20templates%20for%20your%20Autopilot%20device%20enrollment.%20%3CSTRIKE%3EWe'll%20update%20this%20post%20when%20a%20fix%20is%20in!%3C%2FSTRIKE%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EBlog%20post%20updates%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E12%2F19%2F19%20with%20an%20update%20that%20this%20known%20issue%20is%20now%20resolved.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-737137%22%20slang%3D%22en-US%22%3E%3CP%3EWe%E2%80%99ve%20discovered%20a%20bug%20in%20this%20setting%20with%20%3CSTRONG%3EWindows%2010%201809%3C%2FSTRONG%3E%20where%20using%20a%20prefix%20with%20the%20%25RAND%3Ax%25%20macro%20does%20not%20work%20to%20apply%20a%20device%20name%2C%20if%20the%20total%20of%20the%20prefix%20and%20macro%20adds%20up%20to%2015%20or%20more%20characters.%3C%2FP%3E%3C%2FLINGO-TEASER%3E

Updated 12/19/19 - The fix for this issue has been released with the 8C (Third week of August 2019) Windows Update, which is the 3rd week of August (See Windows 10 update servicing cadence).

Note: Any device that has 1809, but doesn’t have the August update will have this issue.

 

When enrolling devices through Autopilot, you can create an Autopilot deployment profile and configure the “Apply device name template” setting to create a device name for Windows 10 1809 and higher devices at initial startup.

 

Spencer account CSP post.jpg

 

We’ve discovered a bug in this setting with Windows 10 1809 where using a prefix with the %RAND:x% macro does not work to apply a device name, if the total of the prefix and macro adds up to 15 or more characters.

 

As a workaround you should ensure that you enter 14 characters or less overall when using device name templates for your Autopilot device enrollment. We'll update this post when a fix is in!

 

Blog post updates:

  • 12/19/19 with an update that this known issue is now resolved.