SCCM 2007 Client doesn't successfully compiled policy

We have McAfee endpoint product installed on windows XP client, we found client without McAfee endpoint product can successfully download package before the program runs, but client with McAfee endpoint product will not download package before the program
runs, instead it will wait to the time for program runs then start download package.
We compare the AgentPolicy log on the normal client vs. failed download client, we found in the failed download client the policy will not successfully compiled, but we didn't see any valuable message for troubleshooting.
Please advise how to troubleshooting this issue.
PS. All McAfee endpoint blocking/restricting function has been disabled.
Regards
Steven

Hi,
Can you please upload the logs file PolicyEvaluator and PolicyAgent.log to Skydrive and post the link here?
Juke Chou
TechNet Community Support

Similar Messages

WSUS Server settings and Migrating SCCM 2007 Clients to SCCM 2012 R2

I am in the process of migrating a site from SCCM 2007 to SCCM 2012 R2.
Whilst doing this I came across the following issue:
The first issue is the workstations are woefully out of date, patch and update-wise, some have never had a patch applied as the branch IT staff are building them from the original disk. The policy is set in the SCCM 2007 client to point the machines at
the 2007 WSUS server, which is not set to deliver any updates to 2007 clients and hasn't been for a while. So as soon as the client is installed they lose the ability to get updates from Microsoft and don't get them from the 2007 WSUS server either.
Issue number 2 is the machines are a mixture of hand-built machines to SCCM 2007 delivered images, the SCCM image is patch using offline patching so they are somewhat up-to-date, but the hand-built machines are not and as there is no standardization on
the Microsoft Update client settings, the IT person on-site sets it to whatever he/she feels like, as it makes no difference once the client is installed and the policy applied.
So, when I come to update the client from 2007 to 2012, the following occurs
The Client uninstalls, and the GPO policy settings for Windows Update are removed.
Depending on the setup of the client initially, some machines are then going to Microsoft for their updates (literally 100s) and although the new client is installed the policy update does not fire to update the Windows Update Policy settings, sometimes
for hours after the install finishes. My thoughts are that it just can't run the policy as it is bogged down by patches updating and, in some cases, rebooting and then updating some more.
As a workaround I have had to go in an physically disable Microsoft Update on these machines, which stops the downloading and eventually allows the policy to apply, after which the machine then begins to receive patches from WSUS in a controlled method during
maintenance windows.
I have tried a number of approaches, even setting the Global Group Policy for Windows Update, but the install still removes the keys and basically sets Windows updates back to whatever it was set before the policy was applied and stays that way until the
new client is installed and the Machine policy reapplied. This can be speeded up by initiating it on the client obviously, but that would mean going to each client or using right-click tools on each machine, which is not an option.
What I would like to know is if there is something I am missing from my methods or is it just that I have never been on a site with such out of date workstations built in such different ways.
Any help would be appreciated.

First note that clients do *not* get updates from WSUS in ConfigMgr. The Windows Update Agent (WUA) must point to the WSUS integrated into ConfigMgr (by virtue of having the SUP installed on it) but this is only to make the update catalog/metadata available
to it. Approving updates in WSUS is unsupported for ConfigMgr.
What you've described above is all working as designed although these clients are falling into a gap between the 2007 and 2012 configuration and thus they are reaching out to Windows Update during this gap and installing updates. To prevent this, you
need to disable automatic updates via a domain group policy. This will prevent all automated WUA activity including installing updates from any source automatically. This will not interfere with ConfigMgr Software Updates in any way though.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2012: push client sccm 2007 client worked but then no deployment is reaching the client

Hi,
We upgraded an sccm 2007 client to sccm 2012 and are deploying a tasks sequence to it.
However, the task sequence is not appearing. Also we cannot connect via client center tools.
Sccm 2012 client seemed to have installed correctly.
Please advise what logfiles to check.
J.
Jan Hoedt

Sccm 2012 client seemed to have installed correctly.
"Seemed to install" or did it really install? Nothing has changed logfile-wise from CM07 to CM12: ccmsetup.log can still be used to examine if the client was installed successfully. LocationServices.log, ClientIDManageStartup.log etc for further communication
troubleshooting.
Torsten Meringer | http://www.mssccmfaq.de

How can I remove the SCCM 2012 client and reinstall SCCM 2007 client on all of our computers

Hello All
We have bit of a problem. Our virtual SCCM 2012 r2 server was deleted and the back solution we had in place keeps failing.
We do have our sccm 2007 server still in place but its only role was imaging as we transferred roles from one to another.
My question is now our support needs to remote into pcs but cant because the CM12 server is gone. How can I remove the 2012 client from all of our companies computers and reinstall the CM07 client so we can remote into computers again.
Thanks in advance!
Phil
Phil Balderos

Run a ccmsetup /uninstall on the clients. You may need to run via PSExec. Then push out the SCCM 2007 client via the 2k7 console.
Cheers
Paul | sccmentor.wordpress.com
Thanks Paul!
I have to do this on over 350 computers and 110 servers. How can I do it on a more massive scale?
Phil Balderos
I would check Torsten's approach first and see if the ccmsetup will uninstall the 2012 version. I'm not sure. Obviously the other way round is fine.
Using PSexec you can script this to call up a txt file of all your servers/computers and run the uninstall.
e.g.
for /f "tokens=*" %a in (computers.txt) do psexec \\%a %WINDIR%\ccmsetup\ccmsetup.exe /uninstall
If your account has privileges on all devices you won't need to add in any username/password credentials. Obviously only devices that are switched on and you have access to will run this.
Cheers
Paul | sccmentor.wordpress.com

Collection in SCCM 2012 of SCCM 2007 clients?

Hi,
I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
Can that be done?
I guess queries can only be run on what sccm 2012 client return on info (I tried a simple query: configuraiton manager client state - version but it only return versions 5.x).
Pls advise.
J
Jan Hoedt

I'd need to make a collection of SCCM 2007 clients in SCCM 2012. This way I know which clients need to be updated.
Can that be done?
Can't you just add the column '(client) version' in the console? Are they displayed then? (Also keep in mind that it's theoretically not possible that CM07 clients can be assigned to a CM12 site)
Torsten Meringer | http://www.mssccmfaq.de

SCCM 2012 client push to SCCM 2007 clients

Hi,
I'd like to upgrade SCCM 2007 clients to SCCM 2012. Their computers appear in SCCM 2012.
I could select them and then select "install client" but there are about 400 to upgrade, some or online some not.
Will the process of upgrade run when the offline clients get online?
J.
Jan Hoedt

If your clients are member of an Active Directory, you could also use a startup script to update the client.
Jason has a very popular script you can use:
http://blog.configmgrftw.com/configmgr-client-startup-script/
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

SCCM 2007 client registration not working.

Hi guys,
i'm in the following situation. Existing SCCM 2007 server at a customers environment. Site is running in Mixed mode. Windows XP clients connected by VPN to the customers infrastructure. The only allowed communication is Port 3333 (http) and Port
3334 (https) from Windows XP to the SCCM Server for Client -> Server Communication. The client is not in the domain, has no DNS and no WINS available. Customer would like to install the SCCM Agent to these computers for hardware inventory purposes.
What I did:
Changed the SCCM Client Communication Port from 80 to 3333 (HTTP)
Changed Site Mode Settings to "Automatically approve all computers" (I know it is not recommended but for first testing, this is ok for us.
Added a host file entry on the Windows XP client to point sccm01.mydomain.local to the appropriate IP Adress of the SCCM Server.
Manually installed the SCCM client on the Windows XP client by using the following command
-> ccmsetup.exe CCMHTTPPORT=3333 CCMHTTPSPORT=3334 SMSMP=sccm01.mydomain.local SMSSLP=sccm01.mydomain.local SMSSITECODE=TST
I see that the client gets installed and shows the correct Site Code etc. but it never appears on the SCCM Server. The ClientIDManagerStartup.log shows that the registration fails:
RegTask - Executing registration task synchronously. 1/1/1601 12:00:00 AM 0 (0x0000)
Evaluated SMBIOS (encoded): 1/1/1601 12:00:00 AM 0 (0x0000)
SMBIOS unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
SID unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
HWID unchanged 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Initial backoff interval: 1 minutes 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Reset backoff interval: 257 minutes 1/1/1601 12:00:00 AM 0 (0x0000)
RegEndPoint: Event notification: CCM_RemoteClient_Reassigned 1/1/1601 12:00:00 AM 0 (0x0000)
RegEndPoint: Received notification for site assignment change from '<none>' to 'TST'. 1/1/1601 12:00:00 AM 0 (0x0000)
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=FALSE 1/1/1601 12:00:00 AM 0 (0x0000)
Computed HardwareID=2:C0D8D94C7EAA20E943DEDC77694E744B8C147C09
Win32_SystemEnclosure.SerialNumber=
Win32_SystemEnclosure.SMBIOSAssetTag=
Win32_BaseBoard.SerialNumber=
Win32_BIOS.SerialNumber=
Win32_NetworkAdapterConfiguration.MACAddress=xx:xx:xx:xx:xx:xx 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040231 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040231 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request message. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Failed to send registration request. Error: 0x80040309 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is not registered. Sending registration request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client registration is pending. 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is pending registration. Sending confirmation request... 1/1/1601 12:00:00 AM 0 (0x0000)
RegTask: Client is pending registration. Sending confirmation request... 1/1/1601 12:00:00 AM 0 (0x0000)
In the CertificateMaintenance.log on the client I can see the following:
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Failed to verify signature for assigned MP. 1/1/1601 12:00:00 AM 0 (0x0000)
Do you have any idea what I'm doing wrong? Did I miss an important step?
Thanks in advance for any suggestion!
Regards
Stefan

Did you add the SCCM server name and IP in LMHOST File ? if not done please do it and check.
are you able to browse the MP URL ?
https://xxxxxxx.xxxx.com/SMS_MP/.sms_aut?mpcert
but not the other one https://xxxxxxxx.xxxx.com/SMS_MP/.sms_aut?mplist
http://www.windows-noob.com/forums/index.php?/topic/2029-managing-workgroup-computers-in-sccm-sms-environment/
http://www.windows-noob.com/forums/index.php?/topic/8977-how-can-i-remotely-control-workgroup-computers-in-system-center-2012-configuration-manager/
Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

SCCM 2007 Client Push Error - CCM.log

Guys,
CLinet push is not working on our SCCM 2007 server. Below is the error message from CCM.log
~ ERROR: Failed to connect to the \\\admin$ share using account 'Machine Account' SMS_CLIENT_CONFIG_MANAGER 2/21/2014 5:01:25 PM 1716 (0x06B4)
I am not sure why admin share is \\\admin$. Please help.

May be you have not set Access Account in
Client Push Installation Properties.
Please Visit the below link for better understanding of Client Push Installation.
http://technet.microsoft.com/en-us/library/bb632380.aspx
-Ashu

SCCM 2007 client installation

Hi All,
When ever i m trying to install SCCM client on windows server 2008 R2 machines, the client is getting installed but i can see only two policies to initiate under Action tab. Also, under ccmsetup\logs i can see only few logs like scan agent ets. but WSUS
handler, update store all are missiny be i need to deploy updates and than check but is this normal to have only two policies to initiate under ACtion tab in configuration manager under control panel?
Regards,

Client logs are under ccm\logs, not ccmsetup.logs. If you only have two actions though, that's means the client hasn't been able establish communication with the site successfully or can't register so you won't have a majority of the logs.
Start by checking clientidstartupmanager.log, clientlocation.log, and locationservices.log.
Jason | http://blog.configmgrftw.com

SCCM 2007 client not install

Dear Exprt,
Please assist me to install client, this my first setup i had followed all guide line but could not success.
in SCCM admin console client discover but client not getting install according to log error i had follow some internet provided steps however still not success, i dont know were i made mistake for server installation.
Kind request for your usual support...
In text:
<![LOG[MPs:]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="2128" file="ccmsetup.cpp:4527">
<![LOG[ SCCMSRV.SCCM-AD.COM]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context=""
type="1" thread="2128" file="ccmsetup.cpp:4542">
<![LOG[Updated security on object C:\Windows\system32\ccmsetup\.]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="0" thread="2128" file="ccmsetup.cpp:8849">
<![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="05:59:35.906+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="2128" file="ccmsetup.cpp:9326">
<![LOG[State message with TopicType 800 and TopicId {3F0B6515-0505-4DF2-881C-F4A358589302} has been sent to the FSP]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="FSPStateMessage" context=""
type="1" thread="2128" file="fsputillib.cpp:730">
<![LOG[Running as user "SYSTEM"]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:2690">
<![LOG[Detected 53138 MB free disk space on system drive.]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:463">
<![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:509">
<![LOG[Client OS Version is 6.1, Service Pack Version 0]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:533">
<![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:535">
<![LOG[Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again.]LOG]!><time="05:59:36.183+-180" date="02-03-2014" component="ccmsetup" context=""
type="1" thread="4004" file="ccmsetup.cpp:2774">
<![LOG[Successfully ran BITS check.]LOG]!><time="05:59:36.937+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:7105">
<![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)]LOG]!><time="05:59:36.968+-180" date="02-03-2014" component="ccmsetup" context="" type="3" thread="4004"
file="ccmsetup.cpp:5969">
<![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="05:59:36.968+-180" date="02-03-2014" component="ccmsetup" context="" type="1" thread="4004" file="ccmsetup.cpp:9326">
<![LOG[State message with TopicType 800 and TopicId {BED7FDFE-DBD7-48F5-853A-A81A87AEED84} has been sent to the FSP]LOG]!><time="05:59:36.984+-180" date="02-03-2014" component="FSPStateMessage" context=""
type="1" thread="4004" file="fsputillib.cpp:730">
[email protected]

"Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 404)"
Is you MP healthy? Based on this message, it is not.
Jason | http://blog.configmgrftw.com

Deploying the SCCM 2012 Client to WES 7 devices that are locked down with the FBWF using 2007 task sequence via WEDM.

I'm wondering how people are migrating their embedded devices that are using the FBWF. I've done some googling and it seems like most people are just re-imaging the devices and after migrating a single device i see why. Its not a pretty process. This will
be a long description but ultimately my question stems more from trying to find a better way to execute the device migration from 2007 to 2012.
Some back ground on my situation might be in order here. I'm in the process of wrapping up our 2007 to 2012 migration. We have a 2007 infrastructure that was a central server with 2 primaries and 286 secondary site servers. I've consolidated that to a single
2012 primary site server that hosts all the main roles. There are 2 more servers in the data centers both operating solely as push distribution points I'll refer to them as 2012 01 02 and 03. I'm over half way through the migration and so far haven't needed
to offload any site roles. There are almost 10,000 clients now reporting to the 2012 site server and almost a 100 field servers pulling content from 2012 02 as their source dp as pull dp is the only way forward for this many devices. I've read the horror stories
of trying spin up 200 plus push dps. We are running PKI. I'm at the point now where i need to start migrating the Windows Embedded Seven Standard clients that have the 2007 sccm client on them with WEDM for write filter handling.
What i'm wondering is if anyone has any pointers for me regarding migrating the WES 7 devices. My plan that i've come up with is to somehow script the process using a 2007 WEDM Task Sequence to try and migrate them over to 2012. Things are complicated as
I need to somehow script the install, the policy checkin, hardware inventory, software inventory, and validate the SCEP client installs before I reboot the device one last time to enable the FBWF. How I handled the SCCM 2007 client install on these devices
when they were provisioned was to just create a batch file that would sleep for ten minutes then check to see if the inventoryagent.log file had been created yet. I realize now that is inefficient as i can kick off the inventory using a WMI method once the
client has installed. Also I need to make sure the machine gets its first policy as that is how it creates the communication using PKI through that first policy transfer and that also finalizes the client install. The biggest piece i'm uncertain about in this
regard is the SCEP client.
I had to change the SCEP client install from yes to no in the default client settings as we have some Mcaffee servers that can't have the SCEP client on them. I have incremental updates enabled on the collection that has the policy that installs the SCEP
client but this will take an unknown amount of time unless i force the environment to update as the device starts in 2012 install, or if I could kick off the SCEP isntall... IDK. I'm also wondering if i should keep the device in the migration process until
i validate it has its proper scep policy applied which I believe can be validated by a registry key somewhere.
Once the 2012 client gets installed will that cause it to lose its place within the 2007 Task Sequence? Considering its going to take a minimum of 2 reboots I'd normally use the task sequence to handle its progression through the process.
I'm also considering trying to use an Orchestrator runbook, as that would be a good way to keep track of the migration process as each device migrates. Especially since this might take several seperate scripts.
I'm going to take a stab at scripting the migration process, but if anyone has any pointers that might make this a less complicated I'd really appreciate it as I've got about 3000 of these devices that need to be migrated over. The other things i've learned
the hard way is any time you have something this complicated over the course of 3000 devices you will run into unknowns and the failure rate increases. I'm in the precarious position of having to not only build this process out but in some situations have
it complete in the shortest amount of time possible as we have sites running 24x7. I know the end users behavior all to well and they will just keep hitting the power button sometimes even though their not supposed to so they can get their device functional
again. In those situations i'd end up, if i'm lucky with a device that no longer has a healthy SCCM client in either environment and the write filter disabled.
So like i said any pointers anyone could throw my way i'd really appreciate. I manually went through the migration process on a single device for proof of concept and ended up with almost 2 pages of pseudo code for my migration script/scripts.
Thanks,
-K.R.

Hi,
In R2 there are some new variables you can use to solve this,
http://ccmexec.com/2014/12/smstsmplistrequesttimeout-value-in-milliseconds/
In Sp1 though adding a step to sleep for 2-5 minuter after reboot and before the application install step is a common workaround.. a powershell command with "Start-Sleep
-s 120" should do it.
/Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2007 to SCCM 2012 CLIENT upgrade

Hi,
We have some Windows XP machines with a SCCM 2007 client, connected to a SCCM 2007 server. Meanwhile some client are already migrated to Windows 7 but still connected to SCCM 2007 (and their packages/collections).
Now we would like to:
-migrate the Windows 7 machines to SCCM 2012 and keep their packages (so no re-run of advertisements) run
-migrate the Windows XP machines by migrating the SCCM 2007 clients then advertise a task sequence (Windows 7) to it
Questions:
-should we push the sccm client from 2007 or from 2012 server to keep the membership of collections?
-if we have to push from 2007, please advise howto: use ccmsetup.exe, the msi (is this the way to go: http://blog.metasplo.it/2012/10/how-to-upgrade-sccm-2007-clients-to.html)?
Please advise.
J.
Jan Hoedt

It doesn't seem to be published on the site.
I'll paste it here. Could you advise?
I would like to test with a cmd, so I made an install.cmd which contains.
@echo on
Cscript ConfigMgrStartup.vbs /ConfigMgrStartup.xml
pause
Then I edited the configmgrstartup.xml:
*Commmented lab1 since I'm not sure what to put there, why put a machine name and why the forward slash?
I'd expect domain\administrator.
*Commented out hotfixes since we don't need it
Launched the cmd but nothing happens, no loggings either.
!-- <Option Name="LocalAdmin" >lab1/dadmin</Option> -->
   <Option Name="SiteCode" >LTF</Option>
   <Option Name="CacheSize">8120</Option>
   <Option Name="AgentVersion">5.00.7804.1000</Option>
   <Option Name="MinimumInterval">0</Option>
   <Option Name="ClientLocation">\\oursccmserver\SMS_PRD\Client</Option>
   <Option Name="MaxLogFile">2048</Option>
   <Option Name="ErrorLocation">\\dfs\ErrorLogs\Clientinstall</Option>
   
   <Option Name="Delay" >5</Option>
   <InstallProperty Name="FSP">oursccmserver.fqdn</InstallProperty>
   <InstallProperty Name="SMSMP">oursccmserver.fqdn</InstallProperty>
   <CCMSetupParameter Name="BITSPriority">HIGH</CCMSetupParameter>
   <CCMSetupParameter Name="noservice" />
   <ServiceCheck Name="BITS" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="winmgmt" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="wuauserv" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="lanmanserver" State="Running" StartMode="Auto" Enforce="True" />
   <ServiceCheck Name="RpcSs" State="Running" StartMode="Auto" Enforce="True" />
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="EnableDCOM" Expected="Y" Enforce="True" Type="REG_SZ"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="EnableRemoteConnect" Expected="Y" Enforce="False" Type="REG_SZ"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="LegacyAuthenticationLevel" Expected="2" Enforce="False" Type="REG_DWORD"/>
   <RegistryValueCheck Key="HKLM\SOFTWARE\Microsoft\Ole" Value="LegacyImpersonationLevel" Expected="2" Enforce="False" Type="REG_DWORD"/>
</Startup>
Jan Hoedt

SCCM 2012 Client Communication Issue with SCCM 2007

My Clients was installed SCCM 2007 client version but somehow those clients reporting to SCCM 2012 Server
Note : My SCCM 2007 Server still active mode . and the SCCM 2007 client IP boundaries was not added into SCCM 2012 server
But still communicating to SCCM 2012 , what is the root cause ?
Best Regard's Krishna

Either, during the client installation the client was manually assigned to the ConfigMgr 2012 site (by specifying the site code), or during the client installation the client was auto assigned to the ConfigMgr 2012 site (that can only happen when there
is an overlap in the boundaries and that doesn't have to be the same type of boundary).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 to SCCM 2012 client migration via Powershell

Hi
I'm looking for a controlled way to migrate a SCCM 2007 server client to SCCM 2012. A push of SCCM Console is no option.
I 'll do all the testing but hoped to gain some time by having these questions answered:
*can an install of SCCM 2012 client be remotely triggered in one go (no uninstall of 2007 needed)?
*if uninstall is needed (of sccm 2007 client), does it need a reboot?
What command to use (preferrably powershell):
\\ourserver\Client\ccmsetup.exe" -argumentlist "SMSSITECODE=sitecode","SMSMP=oursccmserver","SMSCACHESIZE=8000","FSP=oursccmserver","CCMLOGMAXSIZE=104857600"
OR (guess that's the command SCCM is using)
Install-CMClient-DeviceName$ComputerName-IncludeDomainController$False-SiteCodePRD-ForceReinstall$True-AlwaysInstallClient$True-Verbose
J.
Jan Hoedt

do I need to import the machine in SCCM 2012 also or launching the SCCM 2012 install from a SCCM 2007
will do this?
How will you do that? This does not work at all when using client push obviously. You can only use packages/programs to update clients to CM12 in that case and that's something you did not want to do.
Torsten Meringer | http://www.mssccmfaq.de

OSD: upgrade sccm 2007 (XP) client to 2012, then deploy TS

Hi,
We have some Windows XP machines in our SCCM 2007. They are discovered via AD in SCCM 2012.
Now we would like to upgrade their client to SCCM 2012 then deploy (available) a task sequence to it (Windows 7 install). This way users can choose whenever to upgrade to Windows 7.
My questions:
*When I right click an XP/SCCM 2007 client and choose upgrade, nothing happens. How can I troubleshoot/follow the upgrade?
*Should the task sequence (SCCM MDT) contain a particular step or can we use the same as a bare metal (PXE) deploy (we do not want to keep any data from the pc)?
Please advise,
J.
Jan Hoedt

Do I understand it correct, that you are trying a Client Push Installation? If so, then start with looking at the ccm.log on the server-side for errors. That log file contains all the information about the push action.
You should be able to use the same task sequence. Just check the deployment settings and the first action of the task sequence (make sure it restarts in WinPE).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

SCCM 2007 Client doesn't successfully compiled policy

Similar Messages

Maybe you are looking for