MS Office 2010 Customized deployment

1. Using .MSP File
You can use setup.exe /admin to create .MSP custom file for MS Office 2010.
After that use setup.exe /adminfile customfile.MSP to deploy MS Office 2010.

2. Using .XML File

Create DeployOffice2007ProPlus.xml and paste the following content:

************************************************************

*

* display level="none" completionnotice="yes" suppressmodal="yes" accepteula="yes">

*pidkey value="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx">

*companyname value="My Organization">

*optionstate id="ACCESSFiles" state="Local" children="force">
*optionstate id="EXCELFiles" state="Local" children="force">
*optionstate id="GrooveFiles" state="Absent">
*optionstate id="OneNoteFiles" state="Local" children="force">
*optionstate id="OUTLOOKFiles" state="Local" children="force">
*optionstate id="PPTFiles" state="Local" children="force">
*optionstate id="PubPrimary" state="Local" children="force">
*optionstate id="WORDFiles" state="Local" children="force">
*optionstate id="XDOCSFiles" state="Local" children="force">
*optionstate id="SHAREDFiles" state="Local" children="force">
*optionstate id="TOOLSFiles" state="Local" children="force">

*setting id="RemovePrevious" value="ACCESSFiles,EXCELFiles,OUTLOOKFiles,PPTFiles,PubPrimary,WORDFiles">

*/configuration>
***********************************************************

after that you can execute this .xml file with this command:

setup.exe /config DeployOffice2007ProPlus.xml

Remove Office 2007 Pro

In order to remove Office 2007 Pro from your machine you need to use .xml file wich contain Product key of the Office 2007 Pro.

Example:

''configuration product="{90120000-0011-0000-0000-0000000FF1CE}">

''display level="none" completionnotice="no" suppressmodal="yes" accepteula="yes">

''setting id="SETUP_REBOOT" value="NEVER">

''/configuration>


Copy these lines, instead '' at the begining of each line put < and save this file as: SilentUninstallConfig.xml

Configuration product is in setup.xml in ProPlus.WW folder.

After that you can execute this command:

setup.exe /config SilentUninstallConfig.xml /uninstall ProPlus

setup.exe and SilentUninstallConfig.xml should be accesible from the point where you execute this command.

SCCM:PXE: Failed to read PXE settings. The system cannot find the file specified. (Error: 80070002; Source: Windows)

The PXE Boot Image cannot be started. The error message is: No boot file received.
SMSPXE.log has contain this error: The system cannot find the file specified. (Error: 80070002; Source: Windows)
Windows Deployment Service is not started.

Solution:
Windows Deployment Service is stopped. Before to manually run Windows Deployment Service, the following folder and all sub-folders have to be deleted:

C:\Windows\Temp\PXEBootFiles

Take ownership and assign Full permissions and delete them after that.

SCCM 2007-OS Deployment-"No Boot Action for Device (x) found"

This issue occurs when the Task Sequence is advertised to a Collection but in smspxe.log still is a log message "No Boot Action for Device (x) found" where x is random number.

Resolution: It seems there is some caching in SCCM database that cause SCCM not be aware that this Task Sequence has been advertised to the collection.
Remove the manual entry of the computer account from SCCM Database, the collection and the Task Sequence.
After that recreate them again and it should start working.
To remove the computer account you can create Dynamic collection based on MAC address of the NIC.

The query is:
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 inner join SMS_G_System_NETWORK_ADAPTER on SMS_G_System_NETWORK_ADAPTER.ResourceID = SMS_R_System.ResourceId where SMS_G_System_NETWORK_ADAPTER.MACAddress = "xx:xx:xx:xx:xx:xx"

You should modify "xx:xx:xx:xx:xx:xx" with the MAC address of your computer.

Unable to install SCCM client: Error 1904

The SCCM Client is removed and after that can not be installed on Windows XP machine.

In Application log this event is received:

Product: Configuration Manager Client -- Error 1904. Module C:\WINDOWS\system32\CCM\VAppRegHandler.dll failed to register. HRESULT -2147024770. Contact your support personnel.

Solution:

regsvr32 C:\WINDOWS\system32\CCM\VAppRegHandler.dll

Creating SCCM Package for Windows Live Software

If you want to deploy Windows Live products (Writer, MovieMaker, Messenger..)separetely it is not posible because from Microsoft can be dowloaded the package wich contains all products.

Windows live wlsetup-all.exe can be downloaded from here: http://download.live.com

If you try to use some tools to extract this exe as WinZIP, WinRAR, 7-zip it will be without success.

The solution will be to install the whole package by default. After that all these files you can find in:

C:\Program Files (x86)\Common Files\Windows Live\.cache

You just need to search in cache folder.



To make MovieMaker to work you need also to have PhotoLibrary installed. If you want to use Photo Library you should have and MS SQL 2005 Compact Edition.

Add user in "Log on As a Service" with command line

We cannot use GPO to deploy "Log on As a Service" User Assigment Rights because it will modify and overwrite the membership of users or groups. But, we don't want to do that, we just want to add new user without affecting other users or groups.

The solution for this issue is to use Ntrights.exe from Windows Resource Kit.

The right command to add the user or group to "Log on As a Service" is:


ntrights.exe -u user@domain +r SeServiceLogonRight

You can deploy this command with your SCCM and you should include ntrights into the package.