Move client install as part of TS

We have a captured image that I'm deploying as our standard SOE, everything is fine, working well.
We have a couple of dozen PC's that are available for use by the public and are locked down using Faronics DeepFreeze.
I've got the DeepFreeze side worked our fine, create a secondary partition, keep that unfrozen etc.
What I'm stuck on is trying to do is have the SCCM client moved to the secondary partition as part of the TS. I've tried the following:
1. Create a new SCCM client package with the correct parameters of CCMINSTALLDIR and
SMSCACHEDIR
2. Use the parameters section of the TS step
3. Write a powershell script that triggers an uninstall / reinstall using SMSTSPostAction
I'm at my wits end.
It seems that because the CCM client is already installed (due to the capture) any other installation just installs it back to the same place.
Anyone have any experience with this?
Thanks in advance!
EDIT: This is actually for SCCM 2012 R2, looks like I posted in the wrong forum??

Your only options here are to use an image without the agent in it or to configure Deep Freeze to exclude the client directories in the C:\Windows folder.
Jason | http://blog.configmgrftw.com | @jasonsandys

Similar Messages

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

OneDrive for Business sync prompts for ODfB client install

Working with a client that has installed Office 2013 ProPlus on an image that is being deployed. Users currently logon to their computer with a local account (Active Directory in process of being deployed).  User is "migrated" and begins
to logon to Active Directory. User now logs on to the O365 portal and accesses their OneDrive site, not yet populated with documents. User clicks "sync" and is prompted to install a OneDrive for Business client, even though it has
already been installed as part of Office 2013 ProPlus. Install proceeds and Internet Explorer closes. Once install has completed, user logs on to O365 portal and attempts to sync OneDrive.   User is prompted again to install the appropriate
client.
I have tried clearing IE cache, launching IE in InPrivate mode and using Chrome.   Same behavior.
Any suggestions?
Thanks,
[email protected]

New fun behavior noted:
New behavior. Similar scenario:   User logging on to PC with a local account.   Office 2013 ProPlus, including ODfB is installed.   User is NOT currently using ODfB. Using Word
2013, Excel 2013, PPT 2013, Outlook 2013 ( connecting to Office 365 mailbox) and Lync 2013 (connecting to Lync Online) are being used by the users. Users machine is joined to a domain, User local account profile is migrated to domain profile.
User logs into PC with domain account. ( Matching the Office 365 account, typically [email protected] ). User logs into Outlook and Lync with no issues. User logs into the Office 365 Portal, selects OneDrive, and selects Sync.
"Sync this library to your device for easy access" window appears. User selects Sync now.. User is presented with "Sign in Call us overprotective, but we need to verify you account again before opening "https://realgoods-my.sharepoint.com""
windows. User enter his email address and clicks Next. User is then presented with "Sign In" windows and enters User ID and password. User is then presented with the "Overprotective" window. This happens 3 times
until user gets "We cannot connect to the specified SharePoint site." error message.
IE browser cache has been cleared. Steps have been followed to clear all document cache files. sharepoint.com, microsoftonline.com, office365.com have been added to the Trusted Sites zone and added to IE compatibility list.
Any clues on this one as well????
R,
Dale
[email protected]

Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

Hi, I have problem with importing MOV files from SJCAM 4000. MOV files are in supported formats for Adobe Premiere Elements 11. But if I'm importing MOV file, only audio part is imported, video part is not imported. How can I solve this problem?

haben
From looking at the specifications of your camera (SJCam 4000), we know already what video compression your camera is using. It is H.264.
A H.264.mov file should be supported by Premiere Elements 11. On what computer operating system is your Premiere Elements 11 running?
Do you have the latest version of QuickTime installed on your computer? And, are you running QuickTime and Premiere Elements 11 from a
User Account with administrative privileges? Please go to Premiere Elements 11 Publish+Share/Computer/QuickTime to confirm that you find
presets there for the QuickTime choice there.
What are the properties of these H.264.mov files - is it 1080p30 (1920 x 1080p30) or something else? Do you know if this camera is recording with a variable or
a constant frame rate?
Please review and consider and then we will decide what next.
Thank you.
ATR

After migration from sccm 2007, there are many systems with no client installed

Hi Everyone,
We have migrated our environment from SCCM 2007 to SCCM 2012 , And Manual client push installation has been done by HeadQuarter SCCM admins on site code of our region.
But as i see , in all systems collection based on OU, there are approx 50% systems with no client installed.
There may be some stale systems in AD.
Is there any way so that i can list out all Stale or old computers which are not in use anymore records of systems from Active directory and so that i move them to OU for which system discovery is not enabled.
Also, it will very useful if i get more information on lastLogonTimeStamp and such more properties which specifies system as stale or OFF the network for some period..

You could also remove the objects without a client and adjust the settings in the
Options tab of the Active Directory System Discovery Properties. By tweaking those options you can make sure that you're not discovering those old objects in the first place.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Find all systems that do not have configuration manager client installed

Guys I've been installing the SCCM client however I still have a lot of systems where the client has not been installed. Is there some type of report or script that you all run in order to find out who does not have the client installed? Any help with
this is greatly appreciated. So far I have been using a log on script in order to install clients.

Are you using AD system discovery? If so you can create a collection with membership query rule looks like this:
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client is null and SMS_R_System.OperatingSystemNameandVersion
like "Microsoft Windows NT Workstation%"
and SMS_R_System.OperatingSystemNameandVersion like "Microsoft Windows NT Workstation%" -
Take that part out if you want both servers and workstations.

Developer 2000 - Server Install - Client Install

I have Developer 2000 and Oracle database 7.2.3 running on the same HP AlphaServer. I'd like to separate the database from the application and move the database to a separate machine. Is that just a case of installing the database elsewhere and configuring SQL*Net, or would I need to reinstall the Developer 2000 software as a client install on the AlphaServer too?

Hi Christian,
Developer 6i and Developer 2000 are quite separate releases of the same
product and therefore must be in separate homes.
The Oracle 8i Client should also be in a separate home to these two.
If you are referring to Designer 6i, then you can install Designer and
Developer into the same Oracle Home (as they work closely together), but
they MUST be the same release, e.g.:
- Designer 6i and Developer 6i
- Developer 2000 and Designer 2000
We strongly recommend you do NOT mix releases in the same home, such as
Designer 6i and Developer 2000, as you will have problems getting both
products to work (they are essentially incompatible).
Regards,
Designer Product Management

Automation scripts for Instant client install\ add TNS entry

Guys,
I'm trying to develop an VB application,which uses data from an Oracle server residing in my neighbour's system.
My system doesn't have oracle client installed.
So, I've made use of Oracle Instant Client package-OCBC.
Now, I'm looking for an automation script that would do the following in order
1)Uzip the instant client into a directory. (say C:\ondemand\instantclient)
2)Add this directory into the PATH environment variable
3)Set up Service Names with tnsnames.ora ie. Create a TNSNAMES.ORA file to configure my Oracle instance connection.
4)Set the TNS_ADMIN environment variable to be the path to the tnsnames.ora
Can someone help me out with automated scripts?
Thanks,
Bhagat

Don't worry. I've solved it.
One of the files I was using stated: Always set the TNS_ADMIN environment variable or registry setting to the full path of the tnsnames.ora file.
I took that to mean including the "tnsnames.ora". It doesn't. It really does mean just the PATH part.
However, with this corrected, I got the pulldown populated. But with only the first part of the name, from the tnsnames.ora file. tnsnames.ora had mydb.<domain>.com. The pulldown only had mydb. Manually adding the .<domain>.com to it worked.
Now on to the next problem. <GRIN>
Cheers,
Eddie

About novell client install

Hi All
my customer have some branch office in Eu & US, there are some OES File Server, he want to perform data migration to windows server (OES and Windows File Server on the same branch office), but Default NSM Engine Server on Aisa. I want to ask if I install Novell client on windows File Server...the migration-Data traffic only keep on branch office local LAN or still return to Engine Server through WAN(VPN) ?
thanks!!
wyld

On 12/4/2013 2:16 AM, wyldkao wrote:
>
> HI
> I re-read admin guide...the novell client indeed install on Engine
> Server, but I find it said
> ==>"If Agents are deployed as a part of a Novell Storage Manager
> installation, these agents are individually used for migration if the
> Novell Client is installed on them. In order for an agent to participate
> in a migration, the server that has the agent installed must also have
> the Novell Client installed."
>
> If my Engine / Agnet locate in different location (leased line), I
> should install Novell client on Windows File Server let it receive
> command from Engine and direct copy data from OES Server , right ?
>
> wyld
>
>
Yes, it would be best to install the Novell Client and an Agent on that
server.
-- NFMS Support Team

Client Install Issue - SCCM 2012 R2 - Manual Deploy Installed ok

Hello, I have sccm 2012 configured with 2,000 machine approx. It is been used mainly as a Software Deployment tool for now. On checking a recent IE10 upgrade, I noticed that there is a number of machines that do not have the client installed (and thus did
not upgrade IE). I picked 1 machine, searched in SCCM - had no client. I checked all relevant settings:
Boundary for Client in question - ok
Local Client Settings (ip,dns,no firewall, ping sccm ok and vice versa etc).
Once i right clicked to deploy the client, it installed no problem. I checked the ccmsetup log file and the only info it had was from the time that the client was manually deployed (I will attach the log below anyway). I am really puzzled as to why the client
did not install and if this is the issue why IE is not upgrading (it is hard to pinpoint as there are 250 sites approx). The automatic install task works no problem on other machines once the machine goes online.
Any help, would be great. Here is the log (I am fairly new to SCCM btw):
SCCM 2012 R2 - Windows 7 SP1 32 Bit
==========[ ccmsetup started in process 7196 ]==========   ccmsetup   05/02/2015 16:28:39   4100 (0x1004)
Running on platform X86   ccmsetup   05/02/2015 16:28:39   4100 (0x1004)
Launch from folder C:\Windows\ccmsetup\   ccmsetup   05/02/2015 16:28:39   4100 (0x1004)
CcmSetup version: 5.0.7958.1401   ccmsetup   05/02/2015 16:28:39   4100 (0x1004)
In ServiceMain   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required.   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /ForceInstall /config:MobileClient.tcf   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
SslState value: 224   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
CCMHTTPPORT:    80   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
CCMHTTPSPORT:    443   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
CCMHTTPSSTATE:    224   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
CCMHTTPSCERTNAME:       ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
FSP:    COLSCCM01.LC-UK.ORG   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
CCMFIRSTCERT:    1   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Retry time:       10 minute(s)   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
MSI properties:    INSTALL="ALL" SMSSITECODE="COL" FSP="COLSCCM01.LC-UK.ORG" SMSCACHESIZE="10240" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"
ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Source List:   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
                  \\COLSCCM01.lc-uk.org\SMSClient   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
                  \\COLSCCM01.LC-UK.ORG\SMSClient   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
MPs:   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
                  COLSCCM01.lc-uk.org   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
No version of the client is currently detected.   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist.   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Updated security on object C:\Windows\ccmsetup\.   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Sending Fallback Status Point message to 'COLSCCM01.LC-UK.ORG', STATEID='100'.   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Failed to get client version for sending messages to FSP. Error 0x8004100e   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
Params to send FSP message '5.0.7958.1401 Deployment '   ccmsetup   05/02/2015 16:28:39   500 (0x01F4)
State message with TopicType 800 and TopicId {19607F6A-0C46-488C-B28D-36640FB0DF94} has been sent to the FSP   FSPStateMessage   05/02/2015 16:28:40   500 (0x01F4)
Running as user "SYSTEM"   ccmsetup   05/02/2015 16:28:40   500 (0x01F4)
Detected 434753 MB free disk space on system drive.   ccmsetup   05/02/2015 16:28:40   500 (0x01F4)
Checking Write Filter Status.   ccmsetup   05/02/2015 16:28:40   500 (0x01F4)
This is not a supported write filter device. We are not in a write filter maintenance mode.   ccmsetup   05/02/2015 16:28:40   500 (0x01F4)
Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=COL))'   ccmsetup   05/02/2015 16:28:40   500 (0x01F4)
OperationalXml '<ClientOperationalSettings><Version>5.00.7958.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>224</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F0308201D8A00302010202104A263F5C34E3AAAA4C178EF33CA94377300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3134303630383134343831315A180F32313134303531363134343831315A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100A4FF6866BC9622545F811F8008ABDC534E96C9699A3354E990CADB04B1399B29EB80FB844425DEEDD9FE680C57AA0FE05D42CF1D431BB69080D4E7ED91A8255739089A83E4836F28B09331C100B0BAD81AD795EFD01C9ECF8DCE2BE03B52EE3AC35E7003B728E0FA56F145279301189388F3FC90A6C3DA5342C61230550C2B79DECB64AC0958C6DE2D5BF83C3EA29126E231FBEAADBD632F65AF41AC3267DB3986929C46A08AF0BF925A40E15A346B38219CC62C6C0BAC8990C05EA04037458F1853E251D8C16946F845D46CB47884D9EB00543AC8B02A7C099B53F7DE1EBD11AA1272476E5AAF55B2CC38122B62C751D988C81A07D06F87A9F7980D2B3560A90203010001A3383036301E0603551D11041730158213434F4C5343434D30312E6C632D756B2E6F726730140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B05000382010100A0DE29D627EB45EF2D0074AD578B62CE9007918B4316351DB2DBEFF2D0DF52C0FF58B6DE3405C88572ECCFAF2A7B335B234FE7D1E5B0FDA20548FEFE4B9E6AFB45E77627EDB70E2378A3135FB1FC34C2308F0FBD1ADD890DD08D8D6081B73FFF86DE87DBF678A7CAD73AE32BF6EB3B9D1E4E0380D7FBE3E9F9EF49339031636F2B3CC60989B8443B91F9F69F5837025B6CAE64E2D1837FAF712186A02567EA87F9E82FD170C4DEA61DC61C16226450FCBE062948F2219FB5801DF3AF73443349421A7228F5E1372B5CA165D8ABAB9D1B3FEAF22705A473AAAB034C2A289AA7A507550050D6516C2D7BECDE5686F17CC66FBB7D2C439F15644EBF9EF7E8402109</SiteSigningCert></SecurityConfiguration><RootSiteCode>COL</RootSiteCode><CCM>
<CommandLine>SMSSITECODE=COL FSP=colsccm01.lc-uk.org SMSCACHESIZE=10240</CommandLine> </CCM><FSP> <FSPServer>COLSCCM01.lc-uk.org</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState"
Value="0" /></Capabilities><Domain Value="lc-uk.org" /><Forest Value="lc-uk.org" /></ClientOperationalSettings>'   ccmsetup   05/02/2015 16:28:41   500
(0x01F4)
Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown.   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
The MP name retrieved is 'COLSCCM01.lc-uk.org' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>'   ccmsetup
05/02/2015 16:28:41   500 (0x01F4)
MP 'COLSCCM01.lc-uk.org' is compatible   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Retrieved 1 MP records from AD for site 'COL'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Retrived site version '5.00.7958.1000' from AD for site 'COL'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
SiteCode:         COL   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
SiteVersion:      5.00.7958.1000   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Only one MP COLSCCM01.lc-uk.org is specified. Use it.   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Searching for DP locations from MP(s)...   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Current AD site of machine is Millbank   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Local Machine is joined to an AD domain   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Current AD forest name is lc-uk.org, domain name is lc-uk.org   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
DhcpGetOriginalSubnetMask entry point is supported.   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Begin checking Alternate Network Configuration   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Finished checking Alternate Network Configuration   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Adapter {743579BD-D66A-4BF9-B487-2AAC075B9473} is DHCP enabled. Checking quarantine status.   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Adapter {8F25ACE0-AE8A-45DD-BF3D-F1315E2B9974} is DHCP enabled. Checking quarantine status.   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Adapter {8AE4D673-90E8-4FCF-AE50-79474ADC6190} is DHCP enabled. Checking quarantine status.   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Adapter {9AA2CA9C-0C0A-48E3-B67E-F9E574AE9DB2} is DHCP enabled. Checking quarantine status.   LocationServices   05/02/2015 16:28:41   500 (0x01F4)
Sending message body '<ContentLocationRequest SchemaVersion="1.00">
<AssignedSite SiteCode="COL"/>
<ClientPackage/>
<ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0"
UseInternetDP="0">
    <ADSite Name="Millbank"/>
    <Forest Name="lc-uk.org"/>
    <Domain Name="lc-uk.org"/>
    <IPAddresses>
<IPAddress SubnetAddress="10.103.38.0" Address="10.103.38.10"/>
    </IPAddresses>
</ClientLocationInfo>
</ContentLocationRequest>
'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Sending message header '<Msg SchemaVersion="1.1"><ID>{57972056-54D4-461F-B818-D3420A0B5C51}</ID><SourceHost>LCD14572</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:LCD14572:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>COLSCCM01.lc-uk.org</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:41Z</SentTime><Body
Type="ByteRange" Offset="0" Length="1084"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>'   ccmsetup   05/02/2015
16:28:41   500 (0x01F4)
CCM_POST 'HTTP://COLSCCM01.lc-uk.org/ccm_system/request'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Content boundary is '--aAbBcCdDv1234567890VxXyYzZ'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Received header '<Msg SchemaVersion="1.1">
   <ID>{48D22538-0FEA-44E6-AAD2-1829DDED2223}</ID>
   <SourceID>GUID:A5143C3E-EA22-4B93-BFF5-B8B859F869F5</SourceID>
   <SourceHost>COLSCCM01</SourceHost>
   <TargetAddress>direct:LCD14572:LS_ReplyLocations</TargetAddress>
   <ReplyTo>MP_LocationManager</ReplyTo>
   <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
   <Priority>3</Priority>
   <Timeout>600</Timeout>
   <TargetHost>LCD14572</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2015-02-05T16:28:39Z</SentTime><Body
Type="ByteRange" Offset="0" Length="2378"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019106092A864886F70D010702A08201823082017E020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015D30820159020101303630223112301006035504031309434F4C5343434D3031310C300A06035504031303534D5302106A638C8D6A89DE904525D14326BE4DB0300906052B0E03021A0500300D06092A864886F70D01010105000482010027BAE95F5B0DD9F75743E1E40A189091900F78F19367C2A8328F823C63F24229608E7CF02FF2FE76FC61C6A61EF0FE8F19AC75755B88124B13964AE58F971DAB67E47B4DDCAA943B4C27F7AF9B5A0AD1DE956A3AACA26965F5FDAC8659E6263DBB55E025FB305C665AC1AA49972CC937A757EC14F1097DA27AB9998D7CAE332EC135A937A80285C87448AD7B4F4ED059063BCB5032920C65CE16FD32475CD395B279021F62E5C3B534697EDCD68A98D2A654379CCA17056F7B4FAB0346242CE56681F405DB9700FD766FDBD584BB69A4AC088BF3B971BE8B05B723701A22B9D76BB5C063F1BD32B56DB7B3BDC6D827E3D90106F3C1145E04B0629528EA24BD37</Property><Property
Name="AuthSenderMachine">COLSCCM01;COLSCCM01.lc-uk.org;</Property><Property Name="MPSiteCode">COL</Property></Hook></Hooks><Payload Type="inline"/></Msg>'   ccmsetup
05/02/2015 16:28:41   500 (0x01F4)
Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags="16777216"><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="COL" MasterSiteCode="COL"
SiteLocality="LOCAL" IISPreferedPort="80" IISSSLPreferedPort="443"/><LocationRecords><LocationRecord><URL Name="http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002" Signature="http://COLSCCM01.lc-uk.org/SMS_DP_SMSSIG$/COL00002"/><ADSite
Name="Millbank"/><IPSubnets><IPSubnet Address="10.20.0.0"/><IPSubnet Address=""/></IPSubnets><Metric Value=""/><Version>7958</Version><Capabilities SchemaVersion="1.0"><Property
Name="SSLState" Value="0"/></Capabilities><ServerRemoteName>COLSCCM01.lc-uk.org</ServerRemoteName><DPType>SERVER</DPType><Windows Trust="1"/><Locality>LOCAL</Locality></LocationRecord></LocationRecords></Site></Sites><ClientPackage
FullPackageID="COL00002" FullPackageVersion="2" FullPackageHash="DB3D5D115FC93F6275817FB9791864D98D4AF6897339B9D4AB1C0DE456C240A8" MinimumClientVersion="5.00.7958.1000" RandomizeMaxDays="7" ProgramEnabled="false"
LastModifiedTime="30376953;932870912" SiteVersionMatch="true" SiteVersion="5.00.7958.1000" EnablePeerCache="true"/><RelatedContentIDs/></ContentLocationReply>'   ccmsetup   05/02/2015
16:28:41   500 (0x01F4)
Found local location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Discovered 1 local DP locations.   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Got 401 challenge Retrying with Windows Auth...   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
PROPFIND 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002'   ccmsetup   05/02/2015 16:28:41   500 (0x01F4)
Using DP location http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Got 401 challenge Retrying with Windows Auth...   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
GET 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002/ccmsetup.cab'   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
C:\Windows\ccmsetup\ccmsetup.cab is Microsoft trusted.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Successfully extracted manifest file C:\Windows\ccmsetup\ccmsetup.xml from file C:\Windows\ccmsetup\ccmsetup.cab.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Retrieved client version '5.00.7958.1000' and minimum assignable site version '5.00.7845.1000' from manifest   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Checking compatibility of site version '5.00.7958.1000', expect newer than '5.00.7845.1000'   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Site version '5.00.7958.1000' is compatible. Client deployment will continue.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Location 'http://COLSCCM01.lc-uk.org/SMS_DP_SMSPKG$/COL00002' passed site version check.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Loading manifest file: C:\Windows\ccmsetup\ccmsetup.xml   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Successfully loaded ccmsetup manifest file.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Checking if manifest version '5.00.7958.1000' is newer than the ccmsetup version '5.0.7958.1401'   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Running from temp downloaded folder or manifest is not newer than ccmsetup.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/vcredist_x86.exe' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/vcredist_x64.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/vc50727_x86.exe' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/vc50727_x64.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/WindowsUpdateAgent30-x86.exe' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/WindowsUpdateAgent30-x64.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/msxml6.msi' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/msxml6_x64.msi' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/msrdcoob_x86.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/msrdcoob_amd64.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'pkgmgr.exe' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'dism.exe' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'wimgapi.msi' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/MicrosoftPolicyPlatformSetup.msi' is applicable. Add to the list.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'x64/MicrosoftPolicyPlatformSetup.msi' is not applicable.   ccmsetup   05/02/2015 16:28:42   500 (0x01F4)
Item 'i386/WindowsFirewallConfigurationProvider.msi' is applicable. Add to the list.   ccmsetup   05/02/2015 1

Hi, Yes i had a look at the log yesterday. there are errors initially, but then the install completes. I can copy the whole log here, the machine in question is LCD14572. If you could take a look would be great. Still doesnt explain why i had to manually
push the client though:
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154539   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:05:58   3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154539   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:05:58   3648 (0x0E40)
Received request: "2097154539" for machine name: "LCD15000" on queue: "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:05:58   3648 (0x0E40)
Stored request "2097154539", machine name "LCD15000", in queue "Processing".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:05:58   3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 1   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:05:58   3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x12d8. There are now 1 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Submitted request successfully   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Found CCR "2097154540.ccr" in queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
======>Begin Processing request: "2097154539", machine name: "LCD15000"   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   4824 (0x12D8)
Execute query exec [sp_IsMPAvailable] N'COL'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   4824 (0x12D8)
Execute query exec [sp_CP_GetPushRequestMachine] 2097154540   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Successfully retrieved information for machine LCD14589 from DB   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154540   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154540   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154540   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Received request: "2097154540" for machine name: "LCD14589" on queue: "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Stored request "2097154540", machine name "LCD14589", in queue "Processing".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 1   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:00   3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x1d10. There are now 2 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Submitted request successfully   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Found CCR "2097154542.ccr" in queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
======>Begin Processing request: "2097154540", machine name: "LCD14589"   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   7440 (0x1D10)
Execute query exec [sp_IsMPAvailable] N'COL'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   7440 (0x1D10)
Execute query exec [sp_CP_GetPushRequestMachine] 2097154542   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Successfully retrieved information for machine LCD14571 from DB   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097154542   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097154542   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Execute query exec [sp_CP_GetPushMachineName] 2097154542   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Received request: "2097154542" for machine name: "LCD14571" on queue: "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Stored request "2097154542", machine name "LCD14571", in queue "Processing".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 1   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:02   3648 (0x0E40)
----- Started a new CCR processing thread. Thread ID is 0x1768. There are now 3 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:04   3648 (0x0E40)
Submitted request successfully   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:04   3648 (0x0E40)
Getting a new request from queue "Retry" after 100 millisecond delay.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:04   3648 (0x0E40)
Sleeping for 60 minutes for queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:04   3648 (0x0E40)
======>Begin Processing request: "2097154542", machine name: "LCD14571"   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:04   5992 (0x1768)
Execute query exec [sp_IsMPAvailable] N'COL'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:05   5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:05   5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:05   5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:21   4824 (0x12D8)
---> The device LCD15000 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:21   4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:21   4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000.lc-uk.org\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:21   4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:23   7440 (0x1D10)
---> The device LCD14589 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:23   7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:23   7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589.lc-uk.org\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:23   7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:26   5992 (0x1768)
---> The device LCD14571 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:26   5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:26   5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571.lc-uk.org\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:26   5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> The device LCD15000.lc-uk.org does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> Attempting to connect to administrative share '\\LCD15000\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> The device LCD15000 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> ERROR: Unable to access target machine for request: "2097154539", machine name: "LCD15000", access denied or invalid network path.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47
4824 (0x12D8)
Execute query exec [sp_CP_SetLastErrorCode] 2097154539, 53   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
Stored request "2097154539", machine name "LCD15000", in queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154539, 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
Execute query exec [sp_CP_SetLatest] 2097154539, N'02/05/2015 16:06:47', 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
<======End request: "2097154539", machine name: "LCD15000".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:47   4824 (0x12D8)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> The device LCD14589.lc-uk.org does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> Attempting to connect to administrative share '\\LCD14589\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> The device LCD14589 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> ERROR: Unable to access target machine for request: "2097154540", machine name: "LCD14589", access denied or invalid network path.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51
7440 (0x1D10)
Execute query exec [sp_CP_SetLastErrorCode] 2097154540, 53   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
Stored request "2097154540", machine name "LCD14589", in queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154540, 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
Execute query exec [sp_CP_SetLatest] 2097154540, N'02/05/2015 16:06:51', 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
<======End request: "2097154540", machine name: "LCD14589".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:51   7440 (0x1D10)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> The device LCD14571.lc-uk.org does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> Attempting to connect to administrative share '\\LCD14571\admin$' using account 'LC-UK\VAdmin'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account LC-UK\VAdmin (00000035)   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> The device LCD14571 does not exist on the network. Giving up   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
---> ERROR: Unable to access target machine for request: "2097154542", machine name: "LCD14571", access denied or invalid network path.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55
5992 (0x1768)
Execute query exec [sp_CP_SetLastErrorCode] 2097154542, 53   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
Stored request "2097154542", machine name "LCD14571", in queue "Retry".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154542, 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
Execute query exec [sp_CP_SetLatest] 2097154542, N'02/05/2015 16:06:55', 2   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
<======End request: "2097154542", machine name: "LCD14571".   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:06:55   5992 (0x1768)
CCR count in queue "Retry" is 3.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:07:42   6564 (0x19A4)
Sleeping for 634 seconds...   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:07:43   6564 (0x19A4)
Thread has been inactive too long. Closing thread   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:47   4824 (0x12D8)
--- This thread is terminating due to inactivity   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:47   4824 (0x12D8)
----- Terminated CCR processing thread. There are now 2 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:47   4824 (0x12D8)
Thread has been inactive too long. Closing thread   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:51   7440 (0x1D10)
--- This thread is terminating due to inactivity   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:51   7440 (0x1D10)
----- Terminated CCR processing thread. There are now 1 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:51   7440 (0x1D10)
Thread has been inactive too long. Closing thread   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:55   5992 (0x1768)
--- This thread is terminating due to inactivity   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:55   5992 (0x1768)
----- Terminated CCR processing thread. There are now 0 processing threads   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:16:55   5992 (0x1768)
Sleeping for 1 seconds...   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:16   6564 (0x19A4)
The Site Control File has not changed since the last parameter update.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:17   6564 (0x19A4)
Updating Site Parameters   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
MP Ports: 80   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
IISPreferedPort: 80   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
MP SSL Ports: 443   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
IISSSLPreferedPort: 443   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Default MP: COLSCCM01.lc-uk.org   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Default MP Type: 1   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Default MP: [None]   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Certificate Selection Criteria:   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Certificate Store:   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
SSL State: 224   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Select First Certificate: 1   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Certificate Issuers:   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Checking configuration information for server: COLSCCM01.LC-UK.ORG.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Checking configuration information for server: COLSCCM01.LC-UK.ORG.   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Fallback Status Point: COLSCCM01.lc-uk.org   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Install on DC: False   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Option for installing using IP address: 0   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Sleeping for 1200 seconds...   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:18:18   6564 (0x19A4)
Waiting for change in directory "D:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:23:39
2876 (0x0B3C)
Execute query exec [sp_CP_GetNewPushMachines] N'COL'   SMS_CLIENT_CONFIG_MANAGER   05/02/2015 16:28:09   2876 (0x0B3C)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154468, 1   SMS_CLIENT_CONF

Client Installing But Not All Components Are Available Post Install

Hi,
Now I am not positive how the posy client install process works but it seems the CM client normally installs and has only base components, then downloads a policy and installs the other components based on the policy?
I have 2 DP's that is PXE enabled. 1 DP works fine installing the CM client via task sequence on W7. What happens at the other DP is after the task sequence runs it seems like the CM client is stuck and won't install the additional components. The way you
can usually tell there is a problem with the CM client is there are only 6 of the 7 tabs present when you open the CM client and if you click on the Actions tab half the actions are missing. What logs should I be looking at to try and troubleshoot this?
Here is the policy agent log from the client that has the issues described above:
<![LOG[Processing PreShutdown event]LOG]!><time="16:39:11.202+300" date="02-03-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="2832" file="policyevaluatorendpoint.cpp:1234">
<![LOG[Processing PostStartup event]LOG]!><time="16:39:19.344+300" date="02-03-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="1652" file="policyevaluatorendpoint.cpp:1228">
<![LOG[Policy Download Endpoint's message queue is empty; proceeding with maintenance work]LOG]!><time="16:39:19.344+300" date="02-03-2015" component="PolicyAgent_Cleanup" context="" type="1" thread="3000"
file="policyutil.cpp:12671">
<![LOG[Registered for MP notifications.]LOG]!><time="16:39:19.344+300" date="02-03-2015" component="PolicyAgent_PostStartup" context="" type="1" thread="1652" file="startuptask.cpp:113">
<![LOG[Not rerequesting policy on site code change in provisioning mode.]LOG]!><time="16:39:19.375+300" date="02-03-2015" component="PolicyAgent_ReRequestPolicy" context="" type="1" thread="2380"
file="rerequestpolicyendpoint.cpp:252">
<![LOG[Processing PostStartup event]LOG]!><time="17:31:10.918+300" date="02-03-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="2396" file="policyevaluatorendpoint.cpp:1228">
<![LOG[Policy Download Endpoint's message queue is empty; proceeding with maintenance work]LOG]!><time="17:31:10.918+300" date="02-03-2015" component="PolicyAgent_Cleanup" context="" type="1" thread="2236"
file="policyutil.cpp:12671">
<![LOG[Registered for MP notifications.]LOG]!><time="17:31:10.918+300" date="02-03-2015" component="PolicyAgent_PostStartup" context="" type="1" thread="2840" file="startuptask.cpp:113">
<![LOG[Processing PostStartup event]LOG]!><time="17:31:49.368+300" date="02-03-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="2376" file="policyevaluatorendpoint.cpp:1228">
<![LOG[Policy Download Endpoint's message queue is empty; proceeding with maintenance work]LOG]!><time="17:31:49.368+300" date="02-03-2015" component="PolicyAgent_Cleanup" context="" type="1" thread="2780"
file="policyutil.cpp:12671">
<![LOG[Registered for MP notifications.]LOG]!><time="17:31:49.368+300" date="02-03-2015" component="PolicyAgent_PostStartup" context="" type="1" thread="2776" file="startuptask.cpp:113">
<![LOG[Triggered update of user S-1-5-21-1078011946-2056399665-367356602-4899 settings]LOG]!><time="16:31:25.834+300" date="02-04-2015" component="PolicyAgent_RequestAssignments" context="" type="1"
thread="3176" file="policyevaluatorendpoint.cpp:1262">
<![LOG[Processing PostStartup event]LOG]!><time="08:43:15.373+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="3016" file="policyevaluatorendpoint.cpp:1228">
<![LOG[Policy Download Endpoint's message queue is empty; proceeding with maintenance work]LOG]!><time="08:43:15.373+300" date="02-05-2015" component="PolicyAgent_Cleanup" context="" type="1" thread="2156"
file="policyutil.cpp:12671">
<![LOG[Registered for MP notifications.]LOG]!><time="08:43:15.373+300" date="02-05-2015" component="PolicyAgent_PostStartup" context="" type="1" thread="3016" file="startuptask.cpp:113">
<![LOG[Triggered update of user S-1-5-21-1078011946-2056399665-367356602-4899 settings]LOG]!><time="08:43:16.153+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1"
thread="2152" file="policyevaluatorendpoint.cpp:1262">
<![LOG[Requesting Machine policy assignments]LOG]!><time="08:51:06.091+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="2792" file="requestassignmentstask.cpp:1485">
<![LOG[Requesting Machine policy from authority 'SMS:MCT']LOG]!><time="08:51:06.091+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="2792"
file="requestassignmentstask.cpp:1549">
<![LOG[Synchronous policy assignment request with correlation guid {2BC97ED8-61B2-4B0D-AE85-00DDC29EA652} for Machine XXXXX completed with status 80004005]LOG]!><time="08:51:06.597+300" date="02-05-2015" component="PolicyAgent_RequestAssignments"
context="" type="2" thread="2792" file="requestassignmentstask.cpp:1843">
<![LOG[Requesting User policy assignments for 'S-1-5-21-1078011946-2056399665-367356602-4899']LOG]!><time="08:51:15.233+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1"
thread="4968" file="requestassignmentstask.cpp:1489">
<![LOG[Requesting User policy from authority 'SMS:MCT']LOG]!><time="08:51:15.249+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context="" type="1" thread="4968" file="requestassignmentstask.cpp:1549">
<![LOG[Skipping request for user policy assignments due to agent configuration for authority 'SMS:MCT'.]LOG]!><time="08:51:15.249+300" date="02-05-2015" component="PolicyAgent_RequestAssignments" context=""
type="1" thread="4968" file="requestassignmentstask.cpp:1621">
TIA

Clients stuck in provisioning mode are usually due to unexpected reboots or unexpected state changes within the task sequence. Double reboots caused by a handful of software updates are a common culprit as of late. Really, the only way to troubleshoot
this is trial and error. Remove things from your TS and run it again to see if the client agent stays in provisioning mode or not. Start with the Install Software Update task.
Jason | http://blog.configmgrftw.com | @jasonsandys

No classes12.zip included with Linux Oracle 8.1.7 client install??

I noticed on the linux client install - it includes a
lclasses11.zip, but this is not the JDBC classes that come with
Windows clients.
1.) What is the lclasses11 or 12.zip files for?
2.) Do I need to copy Windows client classes12.zip, etc to a
linux client? What aren't these included?
Thanks
CHris

Hi,
I faced a problem that I want a Oracle8 driver for Linux, so I
can connect my DB that installed in NT from Linux, I see that
you face the same problem, I hope you find a solution, so could
you please help me in this, should I install Oracle in the
Linux, or not, from where can I install every thing.
Thanx,
Ahmed.

Nokia C5-03 move newly installed application to me...

Hi,
How do you move your installed application from phone memory to memory card in Nokia C5-03
Regards,
S

Hello Shareen, the application once installed in your phone cannot be moved to memory card. The only option is to remove the application from phone memory and then install it to your memory card.
Nokia C7

Error Message on Web Premium Suite while opening Acrobat that Adobe Acrobat was installed as part of a Suite

Can not open Acrobat Pro 9 out of my adobe creative suite 4 web premium. Keeps giving an error message. Adobe Acrobat was installed as part of a suite. To enable Adobe Acrobat start another component of this suite. I am running Windows 7 64 and already have the CS6 Premium Production Suite loaded on my computer. I really don't need to load all of the Web Premium since I have upgraded to CS6 programs but still need the Acrobat. My hard drive crashed and I've had to start all over again. This is the only glitch and it's becoming very frustrating.
Can't find a link to actually speak to someone at Adobe.

you'll need to install and open some other 32 bit cs4 app.

Cisco VPN client install fails with Error 1722 on Windows 7

Hi,
I am having issues with laptops upgraded from Vista to Windows 7.
Prior to the upgrade they are running Cisco VPN Client 5.0.05.0290. These laptops also have Juniper Network Connect 6.5 and Citrix web client installed. The windows upgrade advisor made no recommendations regarding uninstalling / reinstalling these apps.
I have done an inplace upgade to Windows 7 (Windows Vista Enterprise 32bit to Windows 7 Enterprise 32 bit) and after the install the Cisco client is not working. Uninstalled the client (the uninstall was successful) then reinstalled and the installation fails at Installing Cisco Systems Virtual Adapter - error 1722 there was a problem with the windows installer package.
I have followed the steps for a manual uninstall of the Cisco client and then tried the install again - still not successful. Interestingly (or not) the Juniper Network Connect also fails with the error The Network Connect Virtual adapter driver is not installed properly. This also fails to reinstall after being removed.
I tried removing the VPN clients on another laptop and then running the upgrade but the same errors occured when reinstalling the VPN Client. I have tried the Winfix and DNE patch from Citrix but these fail saying there is a corruption in the application.
On another laptop where only the Cisco VPN client was installed a reinstall was required after the upgrade, but it did install successfully.
On a clean image these applications all install fine, however I have a large number of laptops do upgrade and don't want to do a fresh install and settings migration on all of them.
What files / registry entrys are involved with the DNE adapter so I can manually clear it all out before reinstalling?
Anything else I can do to troubleshoot this issue?
Cheers,
James

You should be able to install the 64 bit version of the Cisco VPN software
Latest version is vpnclient-winx64-msi-5.0.07.0440-k9.exe
You should download and run MCPR.exe first, to clean out any traces of McAfee products that conflict with Cisco VPN.
http://download.mcafee.com/products/licensed/cust_support_patches/MCPR.exe
If there is a problem with vbscript registration on the system - there is a fixit tool from Microsoft for that:
MicrosoftFixit50842.msi
(Using Shrew VPN is a possible workaround.)

Move client install as part of TS

Similar Messages

Maybe you are looking for