SCCM clients automatically changes its site code to another

Hi,
We are running SCCM 2012 in windows server 2008 R2 . We have different sites based on different countries, eg: India, UK and US. My issue is that some of the clients which were reporting to a site is automatically changes its reporting to some other
site. Considering the above countries, I must say that the clients which were reporting to India(IND) is now showing its site code(site assigned) as UK in console. This makes the clients to not to communicate with our server and 'Client activity' is not
showing any status(just blank). Initially I have reinstalled those clients and those were showing correct site code. After few days some among the reinstalled ones and few other clients are again reporting its site code to UK. What might be the issue?
Your suggestions are most appreciated.
Quite strange thing is that when I checked the configuration manager in client side it is showing the correct site code and reporting to the correct server.

Either someone pushed the client from the wrong site or there's a GPO in place that reassigns them. CM clients won't automatically reasign themselves.
Torsten Meringer | http://www.mssccmfaq.de

Similar Messages

Site Code for SCCM Clients installed from Secondary Site Server

Hello,
We have started the implementation of SCCM 2012 R2 at our network. We have setup a Primary site (JFO) server & pushed out the installation of SCCM clients to the local subnet. Things went fine.
We have installed a Secondary site (ATC) at a remote network. We have tested client installation in the installation wizard we specify to install the client from the Secondary server. When SCCM client installed from the Secondary server, the site
code that appears on the client in the control panel->Configuration Manager client settings is the site code of the primary site and not the secondary site.
Is this behavior is normal

Ultimately, secondary sites do *not* manage clients and so will never be assigned to the secondary site. However, do note that resources in the console that represent systems that do not have the client agent may show the site code of the secondary site
if they fall within a boundary group associated with that secondary site. This is done so that client push can be initiated from the correct site. More gory details at http://blog.configmgrftw.com/secondary-sites-and-boundary-groups/
Jason | http://blog.configmgrftw.com | @jasonsandys

Error in push sccm client CcmSetup failed with error code 0x80070643 ccmsetup sccm 2012

i want to push sccm client for all computer i enable automatic side-wide client installation
some computer get error code 0x80070643
ccmsetup sccm 2012 this
when i tray manual installation get same error and ccmsetup.exe stopped

Duplicate of
https://social.technet.microsoft.com/Forums/en-US/3bac4677-46b0-4d96-b63d-a819efcc7f35/error-in-push-sccm-client-ccmsetup-failed-with-error-code-0x80070643-ccmsetup-sccm-2012?forum=configmgrgeneral
Please don't double post.
Jason | http://blog.configmgrftw.com | @jasonsandys

Duplicated site code with another Source Hierarchy

I am attempting to migrate data from my existing SCCM2007 server to the new sccm2012. I get an error after I attempt to gather data. My Site code for sccm2012 is S01, Site code for sccm2007(MLSCCM) is S00. How can I delete existing Source Hierarchy
- Source site code? Then hoping to specify new source hierarchy
Error:
Configuration Manager failed to gather data from xxx.xxx.xxx
The specified source hierarchy contains a site that has the same site code as another site that was previously migrated from a different source hierarchy.
To successfully gather data from this source hierarchy you must remove the site with the duplicate site code from the source hierarchy.
How do I do this??

If I understand correctly you want to delete the existing Source Hierarchy. I have detailed the steps here
http://gerryhampsoncm.blogspot.ie/2013/08/configmgr-2012-sccm-2012-migration-post.html
Basic steps are:
Navigate to Administration > Migration > Source Hierarchy
Right click on the Config Mgr 07 hierarchy and select "Stop Gathering Now"
Now select "Clean Up Migration Data" on the ribbon above.
Select "Yes" to delete the Migration history
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Configuration Manager 2012 R2 client push generator no site code

I am attempting to use the ClientPush Generator.Exe to manual push clients. When I start the program, I do not have a Site Code listed in the drop down box. I only have one site, but it is not listed. Any suggestions please?

Thank you for the response. I am running the app from the correct location logged into the SCCM server with a account with domain admin credentials. Your response got me to thank about right clicking the app and running as an administrator.
When the app is launched that way the Site Code is visible.
Thanks again.

[SCCM 2012 R2] Re-using site code

Hi All,
I have a situation where I need to uninstall SCCM Primary Site because of wrong server name convention. SCCM 2012 documentation do not mention of reusing site code after previous site uninstallation.
Is it possible to use same Site Code for new primary site after uninstall old one?
SCCM 2007 Documentation: Site codes should never be used more than once in a Configuration Manager 2007 hierarchy for active sites. If you have uninstalled a site that was publishing site data to Active Directory Domain Services in preparation for installing
a new Configuration Manager 2007 site with the same site code, you should ensure that the previous site's information has been removed from Active Directory Domain Services, and possibly WINS, before use the old site code for a new Configuration Manager 2007
site. All references to the original site need to be removed from all other sites in the hierarchy, and you need to clean up any objects previously replicated to potential child sites of the new site. If this is not done, any newly replicated objects from
the newly created site could overwrite objects already replicated to the child sites by the previous installation.
SCCM 2012 Documentation: Site codes cannot be used more than one time in a Configuration Manager hierarchy for a central administration site or primary sites. If you reuse a site code, you run the risk of having object ID conflicts in your Configuration
Manager hierarchy. You can reuse the site code for a secondary site if it is no longer in use in your Configuration Manager hierarchy or in the Active Directory forest.
Thank you in advance.
Regards,

I have a CAS (CAS) and One Primary site (AU1) connected to CAS.
I want to install second Primary site (EU1) connected to same CAS (CAS). Server name for EU1 Primary site is wrong and guys that are higher in hierarchy than me want from me to fix the server name.
Reason for everything is always: Politics
So you know that you are begging for trouble by having a CAS. You do also know that all the administration should be done ONLY on the CAS and nowhere else.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM Client Instalaltion failed with error code 1624

Folks,
I am getting clients installation failed exit code 1624 and
CcmSetup failed with error code 0x80070658

- Check the access to the adminshare from the SCCM server
\\computer\admin$
- Run the wbemtest.exe to see if you can connect to the systems namespace
- Verify DNS records on your DNS server
- Renew dns
Ipconfig /flushdns
Ipconfig /registerdns
Kind regards,
Tim
MCITP, MCTS, MCSA
http://directoryadmin.blogspot.com
This posting is provided 'AS IS' with no warranties or guarantees and confers no rights.
"If this thread answered your question, please click on "Mark as Answer"

SCCM Client.msi failed Exist Error Code 1603

Hello ,
I tried my level best failed to figure out the issue
I did WMI rebuild, Restart, re-install client and all
The CCMSETUP.log file giving below error message
C:\windows\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExistCode :1603
Action:
Errormessages:
Nexttry 120 Minutes
Cheer's up
Best Regard's Krishna

MSI (s) (30:D4) [13:40:24:694]: Product: Configuration Manager Client - Update 'CLP1041' could not be installed. Error code 1603. Additional information is available in the log file C:\windows\ccmsetup\Logs\client.msi.log.
MSI (s) (30:D4) [13:40:24:701]: Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: CLP1041. Installation success or error
status: 1603.
MSI (s) (30:D4) [13:40:24:702]: Product: Configuration Manager Client - Update 'CLP1046' could not be installed. Error code 1603. Additional information is available in the log file C:\windows\ccmsetup\Logs\client.msi.log.
MSI (s) (30:D4) [13:40:24:702]: Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: CLP1046. Installation success or error
status: 1603.
MSI (s) (30:D4) [13:40:24:702]: Product: Configuration Manager Client - Update 'CLP2052' could not be installed. Error code 1603. Additional information is available in the log file C:\windows\ccmsetup\Logs\client.msi.log.
MSI (s) (30:D4) [13:40:24:702]: Windows Installer installed an update. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: CLP2052. Installation success or error
status: 1603.
MSI (s) (30:D4) [13:40:24:703]: Note: 1: 1708
MSI (s) (30:D4) [13:40:24:703]: Product: Configuration Manager Client -- Installation operation failed.
MSI (s) (30:D4) [13:40:24:703]: Windows Installer installed the product. Product Name: Configuration Manager Client. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
MSI (s) (30:D4) [13:40:24:704]: Attempting to delete file C:\windows\Installer\f2319c7.msp
MSI (s) (30:D4) [13:40:24:704]: Unable to delete the file. LastError = 32
MSI (s) (30:D4) [13:40:24:704]: Attempting to delete file C:\windows\Installer\f2319c8.msp
MSI (s) (30:D4) [13:40:24:704]: Unable to delete the file. LastError = 32
MSI (s) (30:D4) [13:40:24:704]: Attempting to delete file C:\windows\Installer\f2319c9.msp
MSI (s) (30:D4) [13:40:24:704]: Unable to delete the file. LastError = 32
MSI (s) (30:D4) [13:40:24:708]: Deferring clean up of packages/files, if any exist
MSI (s) (30:D4) [13:40:24:708]: Attempting to delete file C:\windows\Installer\f2319c7.msp
MSI (s) (30:D4) [13:40:24:709]: Attempting to delete file C:\windows\Installer\f2319c8.msp
MSI (s) (30:D4) [13:40:24:709]: Attempting to delete file C:\windows\Installer\f2319c9.msp
MSI (s) (30:D4) [13:40:24:709]: MainEngineThread is returning 1603
MSI (s) (30:E4) [13:40:24:711]: RESTART MANAGER: Session closed.
MSI (s) (30:E4) [13:40:24:711]: No System Restore sequence number for this installation.
=== Logging stopped: 12-09-2014 13:40:24 ===
MSI (s) (30:E4) [13:40:24:713]: User policy value 'DisableRollback' is 0
MSI (s) (30:E4) [13:40:24:714]: Machine policy value 'DisableRollback' is 0
MSI (s) (30:E4) [13:40:24:714]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (30:E4) [13:40:24:714]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (30:E4) [13:40:24:714]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (30:E4) [13:40:24:714]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (30:E4) [13:40:24:714]: Restoring environment variables
MSI (s) (30:E4) [13:40:24:715]: Destroying RemoteAPI object.
MSI (s) (30:04) [13:40:24:715]: Custom Action Manager thread ending.
MSI (c) (EC:C8) [13:40:24:717]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (EC:C8) [13:40:24:717]: MainEngineThread is returning 1603
=== Verbose logging stopped: 12-09-2014 13:40:24 ===
Best Regard's Krishna

HT2737 How to change the redeem code to another email account

I have two email accounts ,and I can't get through to redeem on the other account because I've been hacked on my other account...Now my information to security questions has been changed...The question is how do you transfer the gift card to your other account?

Hi Nag
If the Invoice posted not yet cleared with payment?
you can try with cancel/reverse the invoice posted and then repost with correct GL a/c.

How do I change the assigned site code on a REMOTE client via WMI (C#)?

Hi
I was wondering if it is possible to change the site code on a client remotely via WMI. I have found one or two links to this, eg
http://msdn.microsoft.com/en-us/library/jj874135.aspx
and
http://social.technet.microsoft.com/Forums/systemcenter/en-US/67b671bb-4819-4e7a-a4f6-6cb7ded17722/sccm-2007-change-assigned-site-code-on-clients?forum=configmgrgeneral
However none of these will allow me to change it remotely directly from my machine. I have written a tool which fixes many issues but having difficulty with this one. In the past I have even resorted to copying a script remotely to an affected machine then
setting a remote scheduled task which executes the script. This was effective but very dirty! I find it difficult to believe there is no way to do this directly but can't seem to find anything suggesting it is possible.
Before anyone replies with a 'what are you trying to achieve...' type answer, I have a similar situation to that of the guy in the second link but I would like something more instant.
Many thanks

psexec or winrm will allow you to do this.
Jason | http://blog.configmgrftw.com

Remote Site Code change

Does anyone know of a trick to get the SCCM Client Center (by Roger Zander) to change the site code on a remote system? I change the site and click the blue save floppy disk icon, and no errors but it doesn't work. I found a VBScript
example that does it on the local system but can't get that to work unless I use PsExec.
Ideally I'd like to change the site code for amultiple systems in a list, rather than one at a time. Any suggestions?

Is the site code for a site in the same hierarchy or a new one? If it's in a new hierarchy, chaning the site code of a client will fail because the client des not have the trusted root key for the new hierarchy:
http://blogs.technet.com/b/configmgrteam/archive/2009/04/09/reassigning-a-configuration-manager-client-across-hierarchies.aspx.
If it's the same hierarchy, you need to look at the client log files to figure out what is going wrong, specifically LocationServices.log.
For a script to change the site code en masse, you should be able to use the one posted in the last entry in this thread:
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/90272410-19d8-4bb7-8ad1-fc9ff53aff72.
Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Roaming SCCM Client is not receiving policies from its Default MP

Hi
We have come across situation where a roaming client is unable to receive policies when the client moves from one primary site to another.
As per this link http://technet.microsoft.com/en-us/library/bb633252.aspx it should ideally receive policies from its default MP, which is not happening.
the same client is able to receive the policies when we manually assign the new site code.
Scenario with Example:
Client is from site PS1 and default MP is "Server1"
when the same client travels to another primary site(PS2), it should ideally contact its default management for policies and contact resident MP for content info, this is not happening.
for the same client when manually change the site code to PS2, the client is able to download policies.
Question: why the roaming client is unable to download policies from it default MP..?
Please Advise.
Thanks.
LocationService.log
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:11 AM 3020 (0x0BCC)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:11 AM 3020 (0x0BCC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:13 AM 4968 (0x1368)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:13 AM 4968 (0x1368)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:13 AM 6868 (0x1AD4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:06:17 AM 6868 (0x1AD4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:06:17 AM 6868 (0x1AD4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:09:54 AM 3384 (0x0D38)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:09:54 AM 3384 (0x0D38)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:09:55 AM 3384 (0x0D38)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:09:55 AM 3384 (0x0D38)
GetCurrentManagementPointEx ClientLocation
10/2/2014 8:14:00 AM 3352 (0x0D18)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 8:14:00 AM 3352 (0x0D18)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:06:43 AM 5680 (0x1630)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:06:43 AM 5680 (0x1630)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:06:48 AM 5680 (0x1630)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:06:48 AM 5680 (0x1630)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:09:54 AM 5980 (0x175C)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:09:54 AM 5980 (0x175C)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:13:55 AM 5572 (0x15C4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:13:55 AM 5572 (0x15C4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:15:19 AM 5572 (0x15C4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:15:19 AM 5572 (0x15C4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:20:24 AM 7292 (0x1C7C)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:20:24 AM 7292 (0x1C7C)
GetCurrentManagementPointEx ClientLocation
10/2/2014 9:35:55 AM 5224 (0x1468)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 9:35:55 AM 5224 (0x1468)
Getting Assigned Site ClientLocation
10/2/2014 10:06:34 AM 7188 (0x1C14)
Assigned Site is PS1 ClientLocation
10/2/2014 10:06:34 AM 7188 (0x1C14)
Getting Assigned Site ClientLocation
10/2/2014 10:06:34 AM 7188 (0x1C14)
Assigned Site is PS1 ClientLocation
10/2/2014 10:06:34 AM 7188 (0x1C14)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:09:55 AM 6308 (0x18A4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:09:55 AM 6308 (0x18A4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:13:55 AM 6308 (0x18A4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:13:55 AM 6308 (0x18A4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:13:55 AM 6308 (0x18A4)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:13:55 AM 6308 (0x18A4)
Setting Assigned Site ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Assigning client to site 'PS2' ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:18:52 AM 2624 (0x0A40)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:18:52 AM 2624 (0x0A40)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:18:52 AM 2624 (0x0A40)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:18:52 AM 2624 (0x0A40)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:18:52 AM 6308 (0x18A4)
Getting Assigned Site ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:18:52 AM 6308 (0x18A4)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:18:52 AM 6308 (0x18A4)
Assigned Site is PS1 ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Currently Asssigned Site is PS1 ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Removing client site assignments ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Current Management Point is BELLCMPS01.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:18:52 AM 6308 (0x18A4)
Raising event:
instance of CCM_RemoteClient_Reassigned
ClientID = "GUID:00833D7E-BD35-45F0-811F-CDDA5F0791E9";
DateTime = "20141002141852.870000+000";
LastAssignedSite = "PS1";
NewAssignedSite = "PS2";
ProcessID = 7740;
ThreadID = 7796;
ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
Client assigned to site 'PS2' ClientLocation
10/2/2014 10:18:52 AM 7796 (0x1E74)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:19:50 AM 8092 (0x1F9C)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:19:50 AM 8092 (0x1F9C)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:19:50 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:20:55 AM 3500 (0x0DAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:20:55 AM 3500 (0x0DAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:01 AM 7624 (0x1DC8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:01 AM 7624 (0x1DC8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:01 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:05 AM 7160 (0x1BF8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:05 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:05 AM 7160 (0x1BF8)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:05 AM 7160 (0x1BF8)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:09 AM 836 (0x0344)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:09 AM 836 (0x0344)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:21:18 AM 4528 (0x11B0)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:21:18 AM 4528 (0x11B0)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:22:08 AM 4528 (0x11B0)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:22:08 AM 4528 (0x11B0)
Getting Assigned Site ClientLocation
10/2/2014 10:23:05 AM 8028 (0x1F5C)
Assigned Site is PS2 ClientLocation
10/2/2014 10:23:05 AM 8028 (0x1F5C)
Getting Assigned Site ClientLocation
10/2/2014 10:23:05 AM 8028 (0x1F5C)
Assigned Site is PS2 ClientLocation
10/2/2014 10:23:05 AM 8028 (0x1F5C)
Getting Assigned Site ClientLocation
10/2/2014 10:23:29 AM 6880 (0x1AE0)
Assigned Site is PS2 ClientLocation
10/2/2014 10:23:29 AM 6880 (0x1AE0)
Getting Assigned Site ClientLocation
10/2/2014 10:23:29 AM 6880 (0x1AE0)
Assigned Site is PS2 ClientLocation
10/2/2014 10:23:29 AM 6880 (0x1AE0)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:23:37 AM 5836 (0x16CC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:23:37 AM 5836 (0x16CC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:27:08 AM 3680 (0x0E60)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:27:08 AM 3680 (0x0E60)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:27:18 AM 3680 (0x0E60)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:27:18 AM 3680 (0x0E60)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:28:05 AM 3680 (0x0E60)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:28:05 AM 3680 (0x0E60)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:28:47 AM 3680 (0x0E60)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:28:47 AM 3680 (0x0E60)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:31:14 AM 3680 (0x0E60)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:31:14 AM 3680 (0x0E60)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:39:01 AM 2712 (0x0A98)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:39:01 AM 2712 (0x0A98)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:40:00 AM 2712 (0x0A98)
Getting Assigned Site ClientLocation
10/2/2014 10:40:56 AM 1040 (0x0410)
Assigned Site is PS2 ClientLocation
10/2/2014 10:40:56 AM 1040 (0x0410)
Getting Assigned Site ClientLocation
10/2/2014 10:40:56 AM 1040 (0x0410)
Assigned Site is PS2 ClientLocation
10/2/2014 10:40:56 AM 1040 (0x0410)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:47:33 AM 7084 (0x1BAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:47:33 AM 7084 (0x1BAC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:47:39 AM 6588 (0x19BC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:47:39 AM 6588 (0x19BC)
GetCurrentManagementPointEx ClientLocation
10/2/2014 10:49:46 AM 7084 (0x1BAC)
Current Management Point is BELLCMPS02.BELL.CORP.BCE.CA with version 6487 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation
10/2/2014 10:49:46 AM 7084 (0x1BAC)
The Lightning Khan

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCCM client is connecting to the wrong SCCM site

We have a domain controller say TEST1, on which we have 4 SCCM servers. The SCCM’s have the following site codes
PR1, PR1, PR3 and PR4
We had a Group Policy for client installation created for site ‘PR1’, under ‘Group Policy Management' console in Active directory.
On all sites we have enabled ‘Client Push Installation’. All discovered same computers from TEST1 domain controller.
Now from any SCCM (say ‘PR2’) if we try to push client, the SCCM client machine points to the site code ‘PR1’ only.
Now we have removed the Group Policy and ran ‘gpupdate’.
In Active Directory we don’t see the site information of ‘PR1’ any more.
In the ‘PR1’ site we have removed the overlapping boundaries. We still see the problem.
We want to get the clients of PR2 site connect to the same, and install client successfully. Any help on this would be really
helpful.
Below is an extract of ‘LocationServices.log’ of an SCCM client of ‘PR2’ site
LSRefreshSiteCode: Group Policy Updated the assigned site code <PR1>, which is different than the existing assigned site code
<>. Will attempt re-assignment. LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Won't send client assignment fallback status point message because last assignment message was sent too recently.
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Processing GroupPolicy site assignment.
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Assigning to site 'PR1'
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
LSIsSiteCompatible : Verifying Site Compatibility for <PR1>
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from AD
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
No lookup MP(s) from AD
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Using default DNS suffix test1.test.com
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Attempting to retrieve default management points from DNS
LocationServices
3/12/2014 11:31:12 PM
3920 (0x0F50)
Failed to retrieve DNS service record using _mssms_mp_pr1._tcp. test1.test.com lookup. DNS returned error 9003
LocationServices
3/12/2014 11:31:13 PM
3920 (0x0F50)
No lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:13 PM
3920 (0x0F50)
Failed to resolve 'SMS_SLP' from WINS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
LSGetLookupMP: Failed to resolve lookup MP from WINS with 87D00215. Check if it is published
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
LSGetSiteVersionFromAD : Failed to retrieve version for the site 'PR1' (0x80004005)
LocationServices
3/12/2014 11:31:17 PM     3920 (0x0F50)
Attempting to retrieve lookup MP(s) from AD
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
No lookup MP(s) from AD
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Attempting to retrieve lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Using default DNS suffix test1.test.com
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Attempting to retrieve default management points from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Failed to retrieve DNS service record using _mssms_mp_PR1._tcp. test1.test.com lookup. DNS returned error 9003
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
No lookup MP(s) from DNS
LocationServices
3/12/2014 11:31:17 PM
3920 (0x0F50)
Failed to resolve 'SMS_SLP' from WINS
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
LSGetLookupMP: Failed to resolve lookup MP from WINS with 87D00215. Check if it is published
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
LSIsSiteCompatible : Failed to get Site Version from all directories
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)
Won't send a client assignment fallback status point message because the last assignment error matches this one.
LocationServices
3/12/2014 11:31:22 PM
3920 (0x0F50)

Hi,
The GPO writes the value of the site name the client should use and the values are not removed when you remove the GPO, so you need to clear the registry from those keys to be able to assign it PR2.
http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

ITunes Automatically Change EQ Setting Based On Which Airport Express Streaming? I have two Airport Expresses running at my house. Both are connected to different types of speakers. Neither speaker set has its own equalizer, and both require a different

I have two Airport Expresses running at my house. Both are connected to different types of speakers. Neither speaker set has its own equalizer, and both require a different EQ setting to sound just right. Does anyone know of a way to have iTunes automatically change its EQ setting based on which Airport Express it is streaming to?

I'm in the same boat. I have a 6 zone amplifier running with 6 airport expresses to different rooms inside and outside the house. Each has it's own acoustic characteristics. I'd really love to be able to set each airport to equalize based on my SPL frequency sweep I did for each room.
Setting the eq in itunes won't do it as that is global plus I have many more sources for auiod other than itunes that use the AEs directly.

SCCM client not registering on some machines

Hello,
I am running across a strange problem that is only affecting some machines. We are imaging via OSD task sequence, 2012 R2 and some machines do not register properly with SCCM. When I say not registering, I mean it doesn't get its Site code and
missing most of its actions. Most machines that we image work fine, but the odd one doesn't register using the same task sequence that we use on other PC's. When I watch the task sequence steps go through I noticed that right after the installing SCCM
client step it boots right into windows. Basically skipping the steps we have set afterwards, the next step is to install some software (adobe reader, SCEP, and a few others).
I also noticed it seems to happen more often with certain model machines. I have an HP Z420 and an HP Folio 9470m. These consistently fail to register everytime I image.
I've tried quite a few fixes I found online, but nothing has worked as of yet. The most recent fix I tried was to delete the hardware inventory and then rebuild it. That did not work. Entering SMSMP= in the Setup Windows and Config manager step also did
not work. I also tried entering in our DNS server into the registry under the CCM directory. It appears something is happening during the client install (or not happening). But why only certain machines? Most work fine.
Our fix is to simply re-install the client after imaging, this solution has been working for us but I want to find a more permanent solution.
Any ideas?

Jason,
We have this line in the Setup Config Manager,
PATCH=C:\_SMSTaskSequence\OSD\PNS00002\Updates\configmgr2012ac-r2-kb2970177-x64.msp
Keep in mind, that this same task sequence works fine with most other machines. It almost appears to be model specific. Certain models definitely have more issues registering than others.
I'm still fairly new to SCCM, so if you need more from the logs let me know.
==========[ ccmsetup started in process 2176 ]========== ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on platform X64 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Launch from folder C:\_SMSTaskSequence\OSD\PNS00002\ ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
CcmSetup version: 5.0.7958.1000 ccmsetup 12/8/2013 9:04:50 PM 2180 (0x0884)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Ccmsetup command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Command line: "C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\PNS00002 /config:MobileClient.TCF /status:524 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Copying config file from C:\_SMSTaskSequence\OSD\PNS00002\MobileClient.TCF to folder C:\WINDOWS\ccmsetup\. Return result: 0x0 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
SslState value: 224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPPORT:    80 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSPORT:    443 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSSTATE:    224 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMHTTPSCERTNAME:    ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
FSP:    ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
CCMFIRSTCERT:    1 ccmsetup 12/8/2013 9:04:51 PM 2180 (0x0884)
Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Retry time:       10 minute(s) ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MSI properties:    INSTALL="ALL" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Source List: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
                  C:\_SMSTaskSequence\OSD\PNS00002 ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
MPs: ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
                  None ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
No version of the client is currently detected. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Updated security on object C:\WINDOWS\ccmsetup\. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 12/8/2013 9:04:52 PM 2180 (0x0884)
Downloading file C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Downloading C:\_SMSTaskSequence\OSD\PNS00002\ccmsetup.exe to C:\WINDOWS\ccmsetup\ccmsetup.exe ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 16% complete (262144 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 32% complete (524288 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 48% complete (786432 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 64% complete (1048576 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 81% complete (1310720 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 97% complete (1572864 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
File download 100% complete (1614520 of 1614520 bytes). ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Download complete. ccmsetup 12/8/2013 9:04:53 PM 2180 (0x0884)
Running as user "SYSTEM" ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Detected 118178 MB free disk space on system drive. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Checking Write Filter Status. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Unexpected row count (0) retrieved from AD. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
Failed to get site version from AD with error 0x80004005 ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteCode:         PNS ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
SiteVersion:      ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
No MPs were specified from commandline or the mobileclient.tcf. ccmsetup 12/8/2013 9:04:54 PM 2180 (0x0884)
An MP does not exist on this machine. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Client (5.00.7958.1000) is installed and is the same or lower version. Initiating repair. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Repairing version 5.00.7958.1000 of the client with product code {8864FB91-94EE-4F16-A144-0D82A232049D} ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
No features were excluded and will be excluded. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
MSI PROPERTIES are REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:19:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:19:50 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:20:50 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:20:50 PM 2452 (0x0994)
Next retry in 1 minute(s)... ccmsetup 7/21/2014 12:20:51 PM 2452 (0x0994)
C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi is Microsoft trusted. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Running installation package
Package:     C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi
Log:         C:\WINDOWS\ccmsetup\Logs\client.msi.log
Properties:   REINSTALL=ALL REINSTALLMODE=vmous INSTALL="ALL" PATCH="C:\_SMSTASKSEQUENCE\OSD\PNS00002\UPDATES\CONFIGMGR2012AC-R2-KB2970177-X64.MSP" SMSPROVISIONINGMODE="1" SMSSITECODE="PNS" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0"
CCMFIRSTCERT="1" SMSPUBLICROOTKEY=0602000000A4000052534131000800000100010079C8114BFC23ED5F1FAB06FBFD1CB02C2677B589D873B8447F9D97D24FEC9B8CDE4675B6EC962B8F96DC732E89B443A0ED2F31AE086F4F3427FD58D4FC088E3C8B857096E5D9AEF820EB88FECCCFA7479C900C7FFF598D63C05F44406C60E5E1BBBE505470EBB5843FCF5BF42C5E23D9C7C469150498A1F2C05B94AD5507D2C679CC23F653E17FFCB67700DE9FC37B8D8BFEAD2F9BE5B042AC1AB3FF704DF3B538E6CFDA65385954477F1573178B33473AE13CB04BCB01C26CFED03E1815685D45AD2C9DCCF2F9B7A5BE8EE4EA1205C8AA92D11C6D7B7849D4B150C094D08545B7A34AE0029EB2A31DBB57D338A43FC96BF7153AC9C881A0267F4C0713F011A2 ccmsetup 7/21/2014
12:21:51 PM 2452 (0x0994)
File C:\WINDOWS\ccmsetup\{181D79D7-1115-4D96-8E9B-5833DF92FBB4}\client.msi installation failed. Error text: ExitCode: 1635
Action:
ErrorMessages:
ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
A Fallback Status Point has not been specified. Message with STATEID='313' will not be sent. ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
InstallFromManifest failed 0x80070663 ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)
Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 7/21/2014 12:21:51 PM 2452 (0x0994)

SCCM clients automatically changes its site code to another

Similar Messages

Maybe you are looking for