monitor installation using Software Distribution

[guest]

Using Software Distribution Tools to Install Internet Explorer 8

Step 4: Creating and running a job to distribute the package. After you create the package for Internet Explorer 8, you must create a job to distribute it. This job ...

technet.microsoft.com

technet.microsoft.com/en-us/library/cc985331.aspx

to install the existing package of Office 2010 (We hired a consultant to create the package and installed it on other computers before) on a new computer. It is already over 5 hours, the computer doesn’t shows the new Office 2010. The SCCM agent is running for sure and I can access it remotely using Remote tools. Where do you monitor the installation process or how do you troubleshoot it

[guest]

We can look at client side’s policyagent.log, execmgr.log, and cas.log etc to monitor the program execution status. It is also recommend to review the following article which illustrates a holistic software distribution troubleshooting procedure.



- Troubleshooting SCCM Part VI .....Software Distribution ...

http://blogs.technet.com/b/sudheesn/arc ... ution.aspx



If you have any problem analyze the logs, just let me know and I’ll be glad to help.

[guest]

I did see this message in execmgr.log. What does it mean?

Software Distribution Site Settings for the client are missing from WMI



<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="14:29:58.057+000" date="11-30-2011" component="execmgr" context="" type="3" thread="2840" file="softdistpolicy.cpp:1312">

<![LOG[Software Distribution Site Settings for the client are missing from WMI.]LOG]!><time="14:29:58.164+000" date="11-30-2011" component="execmgr" context="" type="3" thread="2840" file="softdistpolicy.cpp:1312">

<![LOG[Common Client Agent Settings for the client are missing from WMI.]LOG]!><time="14:29:58.164+000" date="11-30-2011" component="execmgr" context="" type="3" thread="2840" file="softdistpolicy.cpp:1413">

<![LOG[Software distribution agent was enabled]LOG]!><time="14:30:35.591+000" date="11-30-2011" component="execmgr" context="" type="1" thread="1088" file="execreqmgr.cpp:5974">

<![LOG[Policy arrived for parent package CBG00005 program Install Office Silent]LOG]!><time="15:31:58.591+000" date="11-30-2011" component="execmgr" context="" type="1" thread="3348" file="execreqmgr.cpp:6456">

<![LOG[Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramOfferReceivedEvent

{

AdvertisementId = "CBG20005";

ClientID = "GUID:F9F3804B-16E4-4A0C-AAEC-5932AB39E322";

DateTime = "20111130213158.716000+000";

MachineName = "CBG001482";

ProcessID = 3860;

SiteCode = "CBG";

ThreadID = 3348;

};

]LOG]!><time="15:31:58.716+000" date="11-30-2011" component="execmgr" context="" type="1" thread="3348" file="event.cpp:525">

<![LOG[The user has logged off.]LOG]!><time="16:19:13.955+000" date="11-30-2011" component="execmgr" context="" type="1" thread="356" file="execreqmgr.cpp:4761">

<![LOG[Execution Manager timer has been fired.]LOG]!><time="16:20:14.000+000" date="11-30-2011" component="execmgr" context="" type="1" thread="324" file="execreqmgr.cpp:5188">

<![LOG[A user has logged on.]LOG]!><time="16:22:15.355+000" date="11-30-2011" component="execmgr" context="" type="1" thread="3236" file="execreqmgr.cpp:4522">

<![LOG[The logged on user is NTDOMAIN\bstorey]LOG]!><time="16:22:15.355+000" date="11-30-2011" component="execmgr" context="" type="1" thread="3236" file="execreqmgr.cpp:4540">

<![LOG[Policy is updated for Program: Install Office Silent, Package: CBG00005, Advert: CBG20005]LOG]!><time="16:34:01.195+000" date="11-30-2011" component="execmgr" context="" type="1" thread="1520" file="execreqmgr.cpp:6711">

[guest]

The sentence marked in Red means that ConfigMgr client cannot read SD settings from WMI. Usually, this can occur when ccmexec process is not fully initiated (during shutdown/startup procedure), and it can also occur when the WMI repository is corrupt. In the latter case, we need to rebuild WMI and reinstall ConfigMgr client to fix the issue.



In our case, the error can be ignored because Software distribution agent wasn’t enabled at that. Actually, from the attached logs, I can see that configMgr client has already detected the “Install Office Silent” policy and the updated version as well. See below.



Policy arrived for parent package CBG00005 program Install Office Silent

Policy is updated for Program: Install Office Silent, Package: CBG00005, Advert: CBG20005



So what we need to check next is that:

1. Confirm that if the content for “Install Office Silent” has been downloaded successfully, this can be checked from either cas.log or execmgr.log. If not, we need to troubleshooting the download problem.

2. If the content has been already downloaded but not executed, we need to check what’s the specific error code the installation returns. This can also be checked from execmgr.log.

[guest]

Well, by looking at the cas.log, I noticed that there is no further info recorded since 12/1/2011 4:36:24. While from execmgr.log, I can see the following:

On 11/30/2011, the policy that “Install Office Silent” has successfully arrived at client side, but no content downloaded event was monitored inside the log.

Policy arrived for parent package 00005 program Install Office Silent execmgr 11/30/2011 3:31:58 PM 3348 (0x0D14)

Policy is updated for Program: Install Office Silent, Package: 00005, Advert: 20005 execmgr 11/30/2011 4:34:01 PM 1520 (0x05F0)

On 12/1/2011, we can see that KB977384 (A client update when ConfigMgr is upgraded to R3) is installed in client side. Since then, there is no further info recorded in execmgr.log.

Content is available for program KB977384 - Advanced Client Patch Install. execmgr 12/1/2011 4:32:27 AM 2748 (0x0ABC)

Executing program msiexec.exe /p sccm2007ac-sp2-kb977384-x86-enu.msp /L*v %TEMP%\sccm2007ac-sp2-kb977384-x86-enu.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous in Admin context execmgr 12/1/2011 4:32:27 AM 2748 (0x0ABC)

Service stopped while program KB977384 - Advanced Client Patch Install is running execmgr 12/1/2011 4:36:23 AM 2432 (0x0980)

Can not continue monitoring the program after service restart because the process exited. Assume failed execmgr 12/1/2011 4:36:23 AM 2432 (0x0980)

Raising event:

[SMS_CodePage(437), SMS_LocaleID(1033)]

instance of SoftDistProgramCompletedSuccessfulMIFEvent

{

AdvertisementId = "20000";

ClientID = "GUID:F9F3804B-16E4-4A0C-AAEC-5932AB39E322";

DateTime = "20111201103624.016000+000";

MachineName = "001482";

MIFDescription = "The operation completed successfully.";

MIFDescription7 = "";

MIFDescription8 = "";

MIFDescription9 = "";

PackageName = "00003";

ProcessID = 2580;

ProgramName = "KB977384 - Advanced Client Patch Install";

SiteCode = "domain";

ThreadID = 2432;

UserContext = "NT AUTHORITY\\SYSTEM";

};

execmgr 12/1/2011 4:36:24 AM 2432 (0x0980)



So from the logs, it looks like that the client upgrade (installing KB977384) has been failed somehow, which halts the client functionality. At the current moment, I’d suggest you manually launch the client update program file from share path \\SCCM-FC01.CHICAGOxxxxxxx.ORG\SMSPKGF$\CBG00003\ in the client. Make sure that the installation is successful. And then trigger a machine policy retrieval cycle. Wait for a while and monitor the issue again. If the update installation fails, please let me know the error it returns word by word.


--------------------------------------------------------------------------------

[guest]

To trigger a policy retrieval cycle, please go to client's control panel, here you will find "Configuraiton manager" applet, double click to open it, switch to Actions tab, select "Machine policy retrieval & evaluation cycle", click initiate action.


--------------------------------------------------------------------------------

[guest]

As KB977384 is a binary update to Configuration Manager client, to verify if it is installed successfully in clients, please go to control panel and open the Configuration Manager applet. On general tab, determine whether the build number is 4.00.6487.2157. If yes, then it denotes that R3 is installed correctly.



After verifying the client version number, let’s re-run the Office advertisement to the target client and monitor the client side logs to see what happens. You can also share me the latest version of SCCM client side logs to me for further review.


--------------------------------------------------------------------------------

[guest]

I tried to install the package to one of windows 7 machine. It doesn't work. I am thinking maybe I didn't do it right. What's the procedure to install an existing software distribution (note: our consultant had created the package and tested it)?

--------------------------------------------------------------------------------

[guest]

Well, by default, the downloaded packages source files will be stored in folders named after package IDs under path C:\windows\systeme32(syswow64)\ccm\cache. And to manually launch the installation file using System account, you may take the following steps:



a. firstly download psexec from the following link into the client side:

http://technet.microsoft.com/en-us/sysi ... 97553.aspx

b. Open a command box and Run psexec -i -s cmd.exe and it will open another command prompt which will be interactive and in system context.

c. After the new command box popped up, execute command e.g.:

xxx.exe <the given parameters>

c. Verify if the execution works.



In the mean time, you may also look at execmgr.log from client side to monitor software distribution execution status.

If anything is unclear, feel free to let me know.


--------------------------------------------------------------------------------