Installing Office 2010 Beta with MDT 2010 November 18, 2009
Posted by tmintner in MDT 2010, Office 2010.Tags: Applications, MDT, Office 2010, Office Customization
2 comments
The Office 2010 Beta went public late last night so you might be wondering how to deploy it with MDT 2010. To do so you first need to extract the files from Microsoft with the command:
ProfessionalPlus.exe /extract:c:\extractedfolder
Now that you have extracted the files you can import Office 2010 directly into MDT 2010 as an application. Go to the Applications node and choose a New Application, choose Application with Source Files and click on Next. Enter in the Application Name information and click on Next. For the source files choose the extracted folder you created earlier and click on Next. Enter a name for the folder and click on Next. For the command line just enter setup.exe and click on Next. Click on Next on the summary screen and the Application will be created.
Now that you have Office 2010 imported as an application you can now go to the Properties of the Application you Created and you should see a new tab that looks like the following:
If you want to customize the installation you can choose to use the Office Customization Tool. For example to set the product key for the installation you would navigate to Licensing and User Interface as shown below:
Just enter your product key and go to File, Save to save your changes.
Now you are ready to install Office 2010!
- Tim Mintner
How to add users to “Remote Desktop Users” Group November 18, 2009
Posted by keithga in MDT 2010, VBscript.add a comment
Someone posted a question recently that I thought was intresting:
What is the correct way to use ZTIGroups.wsf, the Restore Groups MDT action, to populate local group membership of groups that have a space in the name? As a test I’m trying to use CustomSettings.ini to add domain users/groups to the local Remote Desktop Users group. I didn’t find a lot of detail in the MDT docs on doing anything other than Administrators or Power Users.
I had done some work in ZTIGroups.wsf earlier this year. We added the ability to save the list of group names, and create the groups dynamically during restore time, in addition to the ability to add members to the group.
I had done testing with ZTIGroups.wsf, however I didn’t recall testing with the group “Remote Desktop Users” group. How did that work?
I tried running a command:
C:\>cscript ZTIGroups.wsf /Groups1:"Remote Desktop Users" "/Remote Desktop Users1:pickett\keith.garner" /restore /Debug:True /DebugCapture
While looking at the output I noticed that the script was looking for a new property: “RemoteDesktopUsers”, where did that come from?
It turns out that the ZTIGroups.wsf script will look for members using the properly name derived from the name of the group being populated, *without* the spaces in the property name.
So running a deployment with the following properties in the customsettings.ini worked:
Groups001=Remote Desktop Users RemoteDesktopUsers001=pickett\Keith.Garner
Keith
Keith Garner is a Deployment Specialist with Xtreme Consulting Group