I have installed the SCCM client on a number of x64 servers within my environment and I have not had one communicate successfully. Theccmsetup.log says the installation was successful. The client is properly assigned and other ccmsetup.exe installation properties take (cache size, etc). That being said, the client never appears in the console and only a limited number of logs are created. The only log with what appears to be a significant error is the CCMExec.log:CCMExec.log RegisterForLogonfailed(0x80040154).CCMEXEC2/6/20099:34:01AM3752(0x0EA8) Phase1initializationfailed(0x80040154).CCMEXEC2/6/20099:34:01AM3752(0x0EA8) Phase1initializationfailed(0x80040154).CCMEXEC2/6/20099:34:01AM3752(0x0EA8)I have run WMIDiag on a couple of the servers and fixed any WMI Security issues that have arisen. I have uninstalled and reinstalled the client after the WMI fixes and am still having no luck. I've even used the SMS 2003 Toolkit 2ccmdelcert.exe utitlity (at the guidance of another SMS admin), but nothing seems to be working.Here is the command line I am using for installation. It is working on all servers with the exception of x64. Any guidance on how I can get a successful client in stallation on these servers would be greatly appreciated. ccmsetup.exe /mp:SMSSITESERVERSMSSLP=SMSSITESERVER SMSSITECODE=ABC FSP=SMSSITESERVER CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 DISABLECACHEOPT=TRUE SMSCACHEFLAGS=PERCENTDISKSPACE SMSCACHESIZE=50

What logs are created? Does the configuraton manager icon show in the control panel? If so can the server auto detect a site code? Is the server inside of site boundaries? Do you have any overlapping boundaries? John Marcum, Systems Management Architect - www.TrueSec.com

The available logs are: CAS.logCcmExec.logClientLocation.logFSPStateMessage.logLocationServices.logPolicyAgentProvider.logPolicyEvaluator.logRemCtrl.logsetuppolicyevaluator.logsmscliui.logSrcUpdateMgr.log Yes, when I navigate to Control Panel > View x86 Control Panel Icons there is a "Confirguation Manager" icon. When I click "Discover" I recieve a window saying "Automatic site discovery was unsuccessful", however there are no boundaries set on the site so there should therefore be no overlapping boundaries. Thanks for your help.

If there are no boundaries how do you expect the client to communicate to the server? What you are seeing is expected behavior, add boundaies, do a site code detection and a machine policy retrieval.John Marcum, Systems Management Architect - www.TrueSec.com

I have clients functioning in this environment without boundaries. I have a production environment of SMS 2003 SP3 without boundaries. Are they really necessary? I assigned the site through the installation properies. In all other cases it has taken. With the x64 servers I've had to manually assign it. The client recognizes its MP based on the information I've found in the ClientLocation.log.

I have never heard of anyone running SMS or SCCM without boundaries. Who am I to say it's impossible though. I will say it makes no sense, but I won't say it's impossible. How do your clients roam? How do they find a MP if they fall out of the database? Do you not use client push install? If you do use it how are the client install files found? John Marcum, Systems Management Architect - www.TrueSec.com

We have a primary site dedicated to supporting our server environment. It was determined that there was no easy way to set boundaries for the IP addresses of the servers, therefore we moved forward without boundaries. As they are servers, we weren't concerned about them roaming (we have bigger problems if that happens :). The installation method we are using is "Manual Installation". I am physically logging on to the servers, mapping a drive to the client share of the primary site and running ccmsetup.exe from a command prompt.

Okay, I see your point now (sorta) When you open the configuration manager icon does it have the correct site code assigned? Also what's in thePolicyAgentProvider.log and PolicyEvaluator.log files? Any errors? John Marcum, Systems Management Architect - www.TrueSec.com

I know, it's not the best way to do things but it's working (on everything else).Yes, the site code is populated. My ClientLocation.log displays the following. I do have one error in my PolicyEvaluator.log:ClientLocation.log GettingAssignedSiteClientLocation2/3/20091:55:20PM4104(0x1008) SettingAssignedSiteClientLocation2/3/20091:55:26PM4104(0x1008) Assigningclienttosite'ABC'ClientLocation2/3/20091:55:26PM4104(0x1008) DiscoverDefaultMPClientLocation2/3/20091:55:30PM4104(0x1008) SiteCodeisABC;ManagementPointisSITESERVERNAME.DOMAIN.COMClientLocation2/3/20091:55:30PM4104(0x1008) GettingAssignedSiteClientLocation2/3/20091:55:30PM4104(0x1008) ClientiscurrentlynotassignedtoanysiteClientLocation2/3/20091:55:30PM4104(0x1008) RemovingclientsiteassignmentsClientLocation2/3/20091:55:30PM4104(0x1008) Raisingevent: instanceofCCM_RemoteClient_Reassigned { DateTime="20090203185530.459000+000"; LastAssignedSite=""; NewAssignedSite="ABC"; ProcessID=3836; ThreadID=4104; }; ClientLocation2/3/20091:55:30PM4104(0x1008) FailedtosubmiteventtotheStatusAgent.Attemptingtocreatependingevent.ClientLocation2/3/20091:55:30PM4104(0x1008) Raisingpendingevent: instanceofCCM_RemoteClient_Reassigned { DateTime="20090203185530.459000+000"; LastAssignedSite=""; NewAssignedSite="ABC"; ProcessID=3836; ThreadID=4104; }; ClientLocation2/3/20091:55:30PM4104(0x1008) Clientassignedtosite'ABC'ClientLocation2/3/20091:55:30PM4104(0x1008) DiscoverDefaultMPClientLocation2/3/20091:55:30PM4104(0x1008) SiteCodeisABC;ManagementPointisSITESERVERNAME.DOMAIN.COMClientLocation2/3/20091:55:30PM4104(0x1008) SettingCurrentManagementPointClientLocation2/3/20091:55:30PM4104(0x1008) ManagementPointisSITESERVERNAME.DOMAIN.COMClientLocation2/3/20091:55:30PM4104(0x1008) PolicyAgentProvider.log Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'Machine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultMachine'PolicyAgentProvider1/30/20098:31:13AM4488(0x1188) Successfullyupdatednamespace'DefaultUser'PolicyAgentProvider1/30/20098:31:13AM3644(0x0E3C) PolicyEvaluator.log ReceivednotificationthatLocalpolicyhaschanged.PolicyAgent_PolicyEvaluator2/3/20091:55:35PM4184(0x1058) FailedtotriggerMachinesettingsupdate(80070057)PolicyAgent_PolicyEvaluator2/3/20091:55:35PM4184(0x1058)

Lack of site boundaries has no effect on client functinality and merely prevents auto-discovery of the site code and site systems. If you statically assign the site code and SLP as bwilms has done, everything works fine. Definately non-standard, but it works in cases where you might have overlapping boundaries and don't need to worry about roaming.Having said that, what version of Windows is this: 2003 or 2008? Do you have any security software installed -- McAfee, Symantec? Is there a firewall enabled blocking outbound communication? Are you in native mode? Are the systems valid members of the domain? Do you have a security team that likes to intrusively lock things down?Jason | http://myitforum.com/cs2/blogs/jsandys

Jason Sandys said:Having said that, what version of Windows is this: 2003 or 2008? Do you have any security software installed -- McAfee, Symantec? Is there a firewall enabled blocking outbound communication? Are you in native mode? Are the systems valid members of the domain? Do you have a security team that likes to intrusively lock things down? Jason | http://myitforum.com/cs2/blogs/jsandys The servers are Windows Server 2003 SP2 R2 Enterprise x64 Edition SP2. I am not aware of any security software installed (and had another look at Add/Remove Programs to check). Communication has been opened both ways on the firewall for ports 80, 445, and 8530. The entirehierarchy is Mixed Mode. The systems are valid members of the domain. Our security team is pretty "on the ball" about locking things down, but I've been working with them on this and they haven't seen any issues on their side. The strangest thing to me is that the installation functions properly and all other servers, but communication chokes when it comes to these x64 boxes.

I am having a similar issue. Before it came to me, one my other admins had already removed and reinstalled the client as it was not communicating. I noted the same errors stated above. I removed the client and deleted the CCM folder, then reinstalled the client. The installation completed without error. AFterwards, the only logs that were created are CCMEXEC and setuppolicyevaluator. I did not see any errors in setuppolicyevaluator. CCMEXEC had the following errors:Error registering hosted class '{E67DBF56-96CA-4e11-83A5-5DEC8BD02EA8}'. Code 0x80040154CCMEXEC16/09/2009 22:09:246644 (0x19F4)Allowing activation requests on class objects.CCMEXEC16/09/2009 22:09:246644 (0x19F4)Registering endpoint notifications.CCMEXEC16/09/2009 22:09:246644 (0x19F4)Error processing notification query for endpoint 'RemoteToolsAgent'. Query='wql:machine:select * from registrykeychangeevent where hive = 'hkey_local_machine' and keypath ="software\\microsoft\\sms\\client\\client components\\remote control\\user settings"'. Code =0x80041002CCMEXEC16/09/2009 22:09:266644 (0x19F4)Registering for Logon/Logoff notifications.CCMEXEC16/09/2009 22:09:266644 (0x19F4)RegisterForLogon failed (0x80040154).CCMEXEC16/09/2009 22:09:266644 (0x19F4)Phase 1 initialization failed (0x80040154).CCMEXEC16/09/2009 22:09:266644 (0x19F4)Phase 1 initialization failed (0x80040154).CCMEXEC16/09/2009 22:09:266644 (0x19F4)I have ran a WMIDIAG and did not find anything that jumped out at me as being an issue. The log is over 6MB, so i am not sure about posting it here. I also checked the DCOM permissions foe the SMS Agent Host as well as the folder permissions on the Registration folder (as suggested in a MS article I saw), but none of this helped. Does anyone have any ideas/suggestions?ThisWindows 2003 R2 x64 SP2serveris part of a cluster, and the SCCM Client on the other node is working fine. It is running Exchange. Hold your breath, I'll be right back.

Possible solution that worked for me. *** Problem Description *** Clients are not downloading the policy from management point. We installed the SCCM client on 64 bit machine and we found that client install successfully, but when we initiate the Machine Policy Retrieval and Evaluation cycle it says the action has been initiated but its not installing or downloading the policy. We are getting following error in CCMExec.log CCMExec.log ========== Error registering hosted class '{E67DBF56-96CA-4e11-83A5-5DEC8BD02EA8}'. Code 0x80040154 CCMEXEC 9/25/2008 2:41:48 PM 6936 (0x1B18) Allowing activation requests on class objects. CCMEXEC 9/25/2008 2:41:49 PM 6936 (0x1B18) Registering endpoint notifications. CCMEXEC 9/25/2008 2:41:49 PM 6936 (0x1B18) Error processing notification query for endpoint 'RemoteToolsAgent'. Query='wql:machine:select * from registrykeychangeevent where hive = 'hkey_local_machine' and keypath ="software\\microsoft\\sms\\client\\client components\\remote control\\user settings"'. Code =0x80041002 CCMEXEC 9/25/2008 2:41:50 PM 6936 (0x1B18) Registering for Logon/Logoff notifications. CCMEXEC 9/25/2008 2:41:51 PM 6936 (0x1B18) RegisterForLogon failed (0x80040154). CCMEXEC 9/25/2008 2:41:51 PM 6936 (0x1B18) Phase 1 initialization failed (0x80040154). CCMEXEC 9/25/2008 2:41:51 PM 6936 (0x1B18) Phase 1 initialization failed (0x80040154). CCMEXEC 9/25/2008 2:41:51 PM 6936 (0x1B18) ========== We took a procmon and found that ES.dll is not registering properly. There is one patch in that box MS08-049 which is causing a problem to download the policy. <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> *** Resolution *** We removed the patch MS08-049 from the box and rebooted the box. After that we install the client and found that its downloading the policy properly. After that we installed the patch again and found that everything is working properly

Please chech the LocationServices.log for errors. You might find useful information there such as what site code the clietn is actually assign to and what MP it is talking to. If there is error, it would then explain why the client can't communicate with the server.Thanks,Minh.Minh

We removed MS08-049, rebooted the server andrepaired the SCCM client. We were a little concerned as after that it started to reboot on its own. Did this 3 times, then settled down. After that, it started working. We were able to install a number of patches and called it good!Hold your breath, I'll be right back.

This solution has worked for me on each server I have tried so far. Thanks for the continued effort on this thread, everybody!

On x64 computers remember to look at the "View x86 Contol Panel Icons"...Len Havron

Hi I'm seeing something similar with x64 servers - same setup with boundaries as well as we're in the process of migrating all clients into a new site. When I attempt to uninstall KB950974 I'm warned that if it's uninstalled, 29 other security updates might not run properly if I do. So I'd decided against it for the time being as I don't want to break the server. Is anyone aware of a fix for this instead of removing the security update? Seems like it must be a bug if ES.dll is not registering properly? Thanks - Mark.