So here is my deal... I have deployed Windows 7 sp1 32bit and 64 bit on computers at a secondary site. The 32bit machines get the primary site code fine and show up in the SCCM console as they should. The 64bit machines do not get the primary site code and show up with a site code of the secondary server in the console. I can go to a 64bit machine, open the client config manager and see that the site code is empty. If I click discover it finds the primary site and all is good. I would like to avoid doing this step, has anyone ran into anything like this? Did I miss a setting or something somewhere?

How are you deploying the systems and the client agent?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

You have a problem with the assignment process. Check the clientlocation.log and locationsservices.log on the clients in the remote location. Make sure they can query AD for a MP and SLP.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

You have a problem with the assignment process. Check the clientlocation.log and locationsservices.log on the clients in the remote location. Make sure they can query AD for a MP and SLP.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

Hi, You may create a new custom task directly after "Setup windows and ConfigMgr" which calls a VB script (see example) to rediscover the site code: Set oSMSClient = CreateObject ("Microsoft.SMS.Client") Set objWMIService = GetObject("winmgmts:" & "\\" & "." & "\root\ccm") Set objPendingAssg = objWMIService.Get("SMS_PendingSiteAssignment=@") ' quit script if instance does not exist if Err.Number<>0 then wscript.quit end if objPendingAssg.Delete_ oSMSClient.RemoveAssignedSites sNewSite=oSMSClient.AutoDiscoverSite oSMSClient.SetAssignedSite sNewSite,0 Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Systems and client are being deployed with a task sequence.

Both of those logs show errors about it not being able to find the mp, I think it is error 5, sorry not at a machine that has this issue right not. I know the other log shows that it is looking over and over for the new site code. I just don't understand why it only happens on the 64 bit machines.

You have a problem with the assignment process. Check the clientlocation.log and locationsservices.log on the clients in the remote location. Make sure they can query AD for a MP and SLP. Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund I get that, my question is why only on the 64bit computers the x86 computers aren't having the issue.

How are you deploying these systems? The actual client agent differs only slightly between the two architectures so it's not a problem with the client itself and of course your back-end is the same and ConfigMgr doesn't do anything different for different client architectures. That leaves one thing, your OS deployment process.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

How are you deploying these systems? The actual client agent differs only slightly between the two architectures so it's not a problem with the client itself and of course your back-end is the same and ConfigMgr doesn't do anything different for different client architectures. That leaves one thing, your OS deployment process.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

How are you deploying these systems? The actual client agent differs only slightly between the two architectures so it's not a problem with the client itself and of course your back-end is the same and ConfigMgr doesn't do anything different for different client architectures. That leaves one thing, your OS deployment process. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys The systems are being deployed through pxe with a task sequence using a captured image.

How are you deploying these systems? The actual client agent differs only slightly between the two architectures so it's not a problem with the client itself and of course your back-end is the same and ConfigMgr doesn't do anything different for different client architectures. That leaves one thing, your OS deployment process. Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys The systems are being deployed through pxe with a task sequence using a captured image.

How did you create your captured image? Have you tried a clean or new x64 image?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

How did you create your captured image? Have you tried a clean or new x64 image?Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

How did you create your captured image? Have you tried a clean or new x64 image? Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys We created the image through a task sequence, and creating and trying another one is about the only thing we haven't tried.