MDT | Ward Vissers

Deploy Office 2010 with Multiple Languages with MDT 2010

I Like Office 2010. For me it is the best Office version i ever worked with.
MDT 2010 it’s great tool that Microsoft created.
Now i will talk about how you deploy Office 2010 with Multilanguage packs with MDT 2010.

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.

Step 9. Use Group Policy to set the language settings for users

Download the Office 2010 policy template files to your computer. You will find them HERE
Make a new GPO named Office 2010 languages settings it is a user policy.
Under User Configuration in the console tree, right-click Administrative Templates.
Click Add/Remove Templates, and then click Add.
In the Policy Templates dialog box, click the template that you want to add, and then click Open.
After you add the Office 2010 templates, click Close.
Open the Group Policy object (GPO) for which you want to set policy.
Double-click User Configuration and expand the tree under Administrative Templates.
Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.
Select the languages that you want to use for each setting.
Save the GPO.
Go Testing

Where to find the right MDT 2010 logs

Each MDT 2010 script automatically creates log files during its execution. The names of these log files match the name of the script—for example, ZTIGather.wsf creates a log file named ZTIGather.log. Each script also updates a common master log file (BDD.log) that aggregates the contents of the log files that MDT 2010 scripts create. MDT 2010 log files reside in C:\MININT\SMSOSD\OSDLOGS during the deployment process. Depending on the type of deployment being conducted, the log files are moved at the completion of the deployment to either %WINDIR%\SMSOSD or %WINDIR%\TEMP\SMSOSD. For Lite Touch Installation (LTI) deployments, the logs start in C:\MININT\SMSOSD\OSDLogs. They end up in %WINDIR%\TEMP\DeploymentLogs when task sequence execution is complete.

MDT 2010 creates the following log files:

BDD.log: This is the aggregated MDT 2010 log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file.

LiteTouch.log: This file is created during LTI deployments. It resides in %WINDIR%\TEMP\DeploymentLogs unless you specify the /debug:true option.

Scriptname.log: This file is created by each MDT 2010 script. Scriptname represents the name of the script in question.

SMSTS.log: This file is created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, or C:\_SMSTaskSequence, or C:\SMSTSLog.

Wizard.log: The deployment wizards create and update this file.

WPEinit.log: This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE.

DeploymentWorkbench_id.log: This log file is created in the %temp% folder when you specify a /debug when starting the Deployment Workbench.

MDT 2010 Update 1 Beta Released

The Solution Accelerators Team have released Microsoft Deployment Toolkit 2010 Update 1 Beta and would like your feedback.

Download the beta now at https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=8689

MDT 2010 Update 1 provides new capabilities, such as:

· Support for Microsoft Office 2010.

· A new User-driven Installation (UDI) deployment method (formerly known as “Modena”) for Microsoft System Center Configuration Manager 2007. UDI gives information technology (IT) staff control over the deployment experience while empowering users to interact with and customize their operating system deployment through an easy-to-use wizard.

· Improvements to the Deployment Workbench driver import process, detecting each driver’s true supported platforms.

· Many bug fixes and other small improvements.

This release supports the deployment of the Windows® 7; Windows Vista®; Windows XP; Windows Server® 2008 R2; Windows Server 2008; and Windows Server 2003 operating systems. See the Microsoft Deployment Toolkit Documentation Library, which is included with MDT 2010 Update 1, for the complete documentation for this release.

MDT HP,Lenovo,Dell tools for getting the right drivers for a specific model

When you search a driver for a specific model you always go to the HP, Dell, Lenovo, Dell site and then you go to download section and chose the model of your pc/laptop and os version and download the drivers.

The Are some handy tools for you:

Dell Tool:
Dell makes drivers driver CABs which incluse all your drivers for your model and OS.

HP Tool:
HP SoftPaq Download Manager provides a simple, powerful way to download software updates for the HP client PC models in your environment. HP SDM can significantly reduce the amount of time it takes to locate and download updates. SoftPaqs can be downloaded in as few as three easy steps from a single user interface after initial setup.

Lenovo Tool:
ThinkVantage Update Retriever enables you to download update packages from the Lenovo Help Center Web site to a network share repository folder.
This is a search tool. You give the model nummer en os and Update Retriever and scan the Lenovo Help Center Web site for the latest driver

Defrag your Virtual Machines (VMs’)

Just like any other operating system, over time, a disk will become fragmented. Virtual machines are no different. The time that it takes for a disk to become fragmented depends on what data is being added to and removed from the virtual machine hard drive.

Why use MyDefrag instead of the standard Windows defragger?

Much faster.
Totally automatic, extremely easy to use.
Optimized for daily use.
Disk optimization, several strategies.
Directories are placed together.
Reclaims NTFS reserved areas after disk-full.
Maintains free spaces for temporary files.
Can defragment very full harddisks.
Can defragment very large files.
Can defragment individual directories and files.
Can be run automatically with the Windows Scheduler.
Can be used from the commandline.
Can be used as a screen saver.
Can be run from cdrom or memory stick.
Script language, can be customized.
Better voor VCB, VDR, DPM & Snapshots.

When you run MyDeFrag.exe with /verysilent it detect automatically the OS and then install x86 or x64 version from MyDefrag. It’s always installed at c:\program files. You can deploy it with MDT 2010 automatically when installing the OS. Or run it from a network share.

You can use Group Policy Preferences to schedule it.

Restore an Windows 7 Capture with MDT 2010

Step1: Import the Capture Image.

You can find the capture file at \\server\deploymentshare$\Capture or x:\deploymentshare\capture.

If you have already imported Windows 7 DVD.
You can chose for Sysprep and Setup files are not needed. The Setup will copy them automatically when de Capture wil be deployed.

Step 2. Create a Normal Client Task with the OS Capture that you imported.

Capture an Existing Windows 7 install with MDT

You can With MDT capture an existing Windows 7 Install.
1. Creating the Task in MDT

Jou must Chose the OS version witch you want to capture.

2. Create a copy from the Customsettings.ini
Edit the Customsettings.ini with de following text.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipAppsOnUpgrade=YES
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES

4. Connect to the deployement share \\server\deploymentshare$ and go to the folder script and double click on LiteTouch.vbs

4. Don’t forget after the Capture to restore the original customsettings.ini file.

Solution for "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

When you use MDT you see many times the following error:
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Solution 1:
To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder. Open the file in notepad and replace the following code in the MapNetworkDriveEX function:

Case Else
‘ Case &h800704C3 ‘ Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
‘ Case &h8007052E ‘ Logon failure: unknown user name or bad password.
‘ There was a some kind of fatal error.
If ErrDesc <> "" then
MapNetworkDriveEx = ErrDesc
Else
MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "
End if
oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
Exit function
End select

With this code:

Case Else
Err.Clear
On Error Resume Next
oNetwork.MapNetworkDrive chr(sDrive)&":", sShare, False
HasError = err.number
ErrDesc = err.Description
On Error Goto 0
If Err.Number <> 0 Then
‘ There was a some kind of fatal error.
             If ErrDesc <> "" then
                                        MapNetworkDriveEx = ErrDesc
             Else
                                        MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" &    "( 0x" & hex(HasError) & " ) "
             End if
             oLogging.CreateEntry MapNetworkDriveEx & "", iLogType
             Exit function
Else
      Exit Function
End If

End select

Solution 2

Download ZTIUtility.7z and replace the ztiutility.vbs with the one in the ZTIUtility.7z. You need 7zip to unpack the file.

http://support.microsoft.com/kb/977566

MDT 2010 Health Care

MDT 2010 Health Care is een samenvatting van best practices voor het aanpassen, bouw en migreren, en beveiligen van Windows XP, Windows Vista of Windows 7 machines. Ook wordt hier kort beschreven hoe men applicaties kan uitrollen (scripted installs,silent installetie, application packages) als onderdeel van de uitrol. Het gaat om het uitrollen van een standaard desktop voor gemeenschappelijk gebruik. Tevens wordt besproken hoe men de gegeven van een gebruiker mee kan nemen naar de nieuwe werkplek.

Handleidingen:
Healthcare Desktop User State Migration Guide
Automated Build Application Integration Guide
Healthcare MDT 2010 Administrators Guide
Automated Build Healthcare Desktop and Server Guide

Downloaden van de MDT HealthCare doe je hier: MDT HealthCare

Installatie:

Voorbeeld wat Health Care automatisch aanmaakt:

MDT 2010 Deploy per Computer of per Model MDT DataBase Config

Met MDT 2010 kun je ook Applicaties per Model of per Computer deployen.
In het artikel MDT 2010 Deploy per Computer of per Model heb ik uitgelegd om de juiste te achter halen.

Per Computer:

Per Model (Getest met een Virtuele XP Machine):

Tag: MDT

Deploy Office 2010 with Multiple Languages with MDT 2010

Like this:

Where to find the right MDT 2010 logs

Like this:

MDT 2010 Update 1 Beta Released

Like this:

MDT HP,Lenovo,Dell tools for getting the right drivers for a specific model

Like this:

Defrag your Virtual Machines (VMs’)

Like this:

Restore an Windows 7 Capture with MDT 2010

Like this:

Capture an Existing Windows 7 install with MDT

Like this:

Solution for "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed"

Like this:

MDT 2010 Health Care

Like this:

MDT 2010 Deploy per Computer of per Model MDT DataBase Config

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this:

Share this:

Like this: