I have been tasked with ensuring all our SCCM clients are pointed back to the right SCCM Server (SiteCode). The ADM file (ConfigMgr2007Assignment.adm) works when then the 32bit sccm client is running on a 32bit OS. The problem i run into is when the 32bit SCCM client runs on a 64bit OS. We can NOT use autodiscover as there are MANY SCCM implementations where I work (large environment). The ONLY way i've found to control the 32bit SCCM client on a 64BIT OS is to use Group Policy preferences and put down the following registry key: HKLM\Software\Wow6432Node\Microsoft\SMS\Mobile Client\ RegZword: GpRequestedSiteAssignmentCode Value: CM0 (this is our sitecode). I've seen other threads that say "the ConfigMgr2007Assignment.adm" will controlthe 32bit sccm client on 64bit OS. To me, this is NOT the case. In my situation, without the key mentioned above, a 32bit sccm client on 64bit OS will find a different SCCM implementation. I know allof this can be solved with proper boundaries from the other SCCM implementations but i can not work with them. Am I doing somehting wrong? Is this a bug/known problem? Or is this what others are doing as well?

Not really a bug per-se but definitely an oversight. You can open the ADM file and edit it also to include the Wo6432Node registry key. Setting this via GPP is no different though. Both ways are simply setting a registry value. Make sure you keep this in mind when you do a migration and don't foget you are essentially hard-coding clients to a site -- this has tripped up many a migration.Jason | http://blog.configmgrftw.com

Im glad that it wasn't me just being crazy. So you're saying open the adm file via text editor or something to and add the registry information in there? I'll have to take a look at this tomorrow when i get to work.

You mention "hard-coding". The ADM file also hard codes, correct?. The only difference is for clients to utilize the GPP, they need client side extensions to understand. The ADM file will work natively on both XP and Windows 7 (albeit, windows 7 already has CSE installed). I see your an MVP on this, how come there is no KB talking about this situation?

You are correct with the hard-coding and the use of GPP: both just set a registry value which can be done in a variety of methods. The .adm file format is documented but you should be able to edit it with little issue as its farily straight-forward. As for the KB, KBs are only created by CSS in direct response to customer cases and support issues. So, unless you're willing to call CSS and request that they create a KB, one won't get created.Jason | http://blog.configmgrftw.com

Good ole Microsoft. Thanks for your comments. They are much appreciated. One last question. Will placing this wow6432 registry key cause harm to an X86 machine. Our OU structure does not separate x86 from x64. Will pushing this GPO down to ALL COMPUTERS cause harm. In testing it has not harmed x86 machines. Looking for feedback.

No, it won't cause any harm but you may want to create a simple WMI filter to apply it to x64 systems only just to make sure it/you don't get blamed for anything.Jason | http://blog.configmgrftw.com

That's exactly what i'm planning to do. Much appreciated for your comments.