Tag: Deployment

Microsoft Deployment Toolkit (MDT) 2010 Update 1 is RTM

Microsoft has released a new version of MDT 2010 named Update 1.

It’s a great tool im loving it.

What new:

For System Center Configuration Manager 2007 users:

  • New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.

  • Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.

For Lite Touch Installation:

  • Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
  • Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.

Bug Fixes and small improvements

  • LTI Wizard performance improvement. The LTI Wizard now takes less time to initialize and shows up faster.
  • Issue in validating connection to the server fixed. In a few scenarios, MDT 2010 used to report the error message, "A connection to the distribution share could not be made" when a task sequence is run. The Microsoft Support article, “Error message when you use MDT 2010: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed,’” at http://support.microsoft.com/kb/977566 describes this issue in detail. This issue has been fixed in MDT 2010 Update 1.
  • Support for installing Windows 7 roles and features. MDT 2010 Update 1 adds support for installation of Windows 7 operating system roles and features.
  • Looping issue with x64 custom Windows images fixed. In MDT 2010, ZTI–System Center Configuration Manager deployments could get into an infinite loop when deploying an x64 Windows image captured by LTI. This issue has been fixed in MDT 2010 Update 1
  • Error handling improvements in MDT task sequence templates. In MDT 2010, task sequences appear to finish successfully even when they really failed. These issues are fixed in MDT 2010 Update 1.

Download the new version HERE 😀

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.
image

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.

SDM_IM 

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
image

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.

image image
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. 
image image
image  image

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
2010-04-18_134159 2010-04-18_134127
Jou must Chose the OS version witch you want to capture.

2010-04-18_134151 2010-04-18_134213
2010-04-18_134231 2010-04-18_134317
2010-04-18_134327 2010-04-18_134336

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
2010-04-15_162332 2010-04-15_162453

2010-04-15_1626352010-04-15_162645

2010-04-15_162659
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

Microsoft Enterprise Desktop Virtualization (MED-V) 1.0 SP1 – now available for Windows 7

There is a new version of MDOP: MDOP 2010 refresh. MDOP 2010 includes:
– Microsoft Enterprise Desktop Virtualization (MED-V) 1.0 SP1 – now available for production deployment on Windows 7
– Microsoft Application Virtualization (App-V) 4.6 – localized client versions and additional languages support

Existing MDOP customers can download the MDOP 2010 Refresh at the Volume Licensing Service Center (VLSC).  For evaluation, MDOP 2010 Refresh can be downloaded from MSDN and TechNet.

What’s new in MED-V 1.0 SP1?
– Support for Windows 7 hosts – 32-bit and 64-bit
– MED-V server support for Windows Server 2008 R2
– Support for Japanese Windows versions

VMWare View GPO settings

Group Policy settings die je moet zetten onder Remote Desktop

image

VMWare View Client GPO settings
– Enable the shade
– Pin the shade
– Don’t check monitor alignment on spanning
– Color depth
– Desktop background
– Show contents of window while dragging
– Menu and window animation
– Themes
– Cursor shadow
– Font smoothing
– Desktop composition
– Audio redirection
– Redirect drives
– Redirect printers
– Redirect serial ports
– Redirect smart cards
– Redirect clipboard
– Redirect supported plug-and-play devices
– Bitmap caching
– Shadow bitmaps
– Cache persistence active
– Enable compression
– Windows key combination redirection
– Bitmap cache file size

The VMware View ADM files can be found on the following place:

“C:\Program Files\VMware\VMware View\Server\Extras\GroupPolicyFiles”

– vdm_agent.adm contains properties relating to the authentication and
environmental components of a client desktop controlled by View Agent
-  vdm_client.adm contains properties relating to the configuration parameters of
View Client
– vdm_server.adm contains properties relating to View Connection Server
– vdm_common.adm contains properties relating to all components of View Manager
– pcoip.adm PCOIP Performance properties

Meer hierover vindt je in VMWare View Manager Administration Guide & VMWare XP deployment Guide

Installeren VMWare View Connection Server 4

Prerequisites

VMware View Connection Server
• Pentium IV 2.0Ghz processor or higher — dual processors are recommended
• 2GB RAM or higher — 3GB RAM is recommended for deployments of 50 or more View Manager desktops. VMware View connection server can handle 2,000 connections in clear mode and 750 in tunneled mode.
• One or more 10/100Mbps network interface controllers (NIC) — 1Gbps NIC is recommended

Supported Operating Systems
The VMware View Connection Server can be installed on the following 32-bit operating systems:
• Windows Server 2003 R2 Standard Edition with SP2
• Windows Server 2003 Standard Edition with SP2
• Windows Server 2003 R2 Enterprise Edition with SP2
• Windows Server 2003 Enterprise Edition with SP2

VMware View Connection Server Licences:
• VMware View Manager
• VMware View Manager with View Composer
• VMware View Manager with View Composer, and Offline Desktop

image image
image image
image image

image image

Translate »