Monday, May 31, 2010

Add/Remove Components in MS Office 2007 Pro

To Add or Remove Components in MS Office 2007 Pro you can use this command:

setup.exe /config Add_remove_comp.xml /modify "ProPlus"

where Add_remove_comp.xml is a modified XML file which contains Office components and "ProPlus" is MS Office 2007 version.


*configuration product="ProPlus">

*Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

*Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" />

*PIDKEY Value="Office ser no" />

*USERNAME Value="user name" />

*COMPANYNAME Value="Company name" />

*INSTALLLOCATION Value="%programfiles%\Microsoft Office" />

*OptionState Id="ACCESSFiles" State="Absent" />
*OptionState Id="EXCELFiles" State="Absent" />
*OptionState Id="GrooveFiles" State="Absent" />
*OptionState Id="OneNoteFiles" State="Absent" />
*OptionState Id="OUTLOOKFiles" State="Local" Children="force" />
*OptionState Id="PPTFiles" State="Absent" />
*OptionState Id="PubPrimary" State="Absent" />
*OptionState Id="WORDFiles" State="Local" Children="force" />
*OptionState Id="VisioPreviewerFiles" 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="Reboot" Value="Never" />


Copy these lines into xml file and instead * at the begining of each line put "<"

You can customize our Office 2007 installation using State="Local" Children="force" for components that you want to be installed or State="Absent" for applications that you want to be removed or not installed.

Friday, May 28, 2010

How to change the listening port for Remote Desktop

Start Registry Editor.

Locate and then click the following registry subkey:


On the Edit menu, click Modify, and then click Decimal.

Type the new port number, and then click OK.

Quit Registry Editor.

To enable Remote Desktop remotely by using the registry

1.On any computer that is running a version of Windows Server 2003 or Windows XP Professional, click Start, click Run, type regedit, and then click OK.

2.On the File menu, click Connect Network Registry.

3.In the Select Computer dialog box, type the computer name and then click Check Names.

4.In the Enter Network Password dialog box, provide Domain Admins credentials for the domain of the server, and then click OK.

5.After the computer name resolves, click OK.

6.In the computer node that appears in the Registry Editor, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server.

7.In the console tree, click Terminal Server and then, in the details pane, double-click fDenyTSConnections.

8.In the Edit DWORD Value box, in Value data, type 0, and then click OK.

9.To implement the change, reboot the server remotely, as follows:

Open a command prompt, type the following, and then press Enter:

shutdown -m \\ DomainControllerName -r

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">


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

setup.exe /config DeployOffice2007ProPlus.xml

Thursday, May 27, 2010

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.


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

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

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


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.

Tuesday, May 18, 2010

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.

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


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

Friday, May 14, 2010

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.