System Center Virtual Machine Manager 2012 Beta Evaluation

System Center Virtual Machine Manager 2012 delivers industry leading fabric managment, virtual machine management and services deployment in private cloud environments. Virtual Machine Manager 2012 offers key new features that include hypervisor creation and management, network management, storage management, private cloud creation, self-service usage and service creation. It features deep investments in server application virtualization, service design and service modeling all of which can be used to efficiently offer an on-premises private cloud.

Feature Summary

  • Fabric Management
    • Hyper-V and Cluster Lifecycle Management – Deploy Hyper-V to bare metal server, create Hyper-V clusters, orchestrate patching of a Hyper-V Cluster
    • Third Party Virtualization Platforms – Add and Manage Citrix XenServer and VMware ESX Hosts and Clusters
    • Network Management – Manage IP Address Pools, MAC Address Pools and Load Balancers
    • Storage Management – Classify storage, Manage Storage Pools and LUNs
  • Resource Optimization
    • Dynamic Optimization – proactively balance the load of VMs across a cluster
    • Power Optimization – schedule power savings to use the right number of hosts to run your workloads – power the rest off until they are needed
    • PRO – integrate with System Center Operations Manager to respond to application-level performance monitors
  • Cloud Management
    • Abstract server, network and storage resources into private clouds
    • Delegate access to private clouds with control of capacity, capabilities and user quotas
    • Enable self-service usage for application administrator to author, deploy, manage and decommission applications in the private cloud
  • Service Lifecycle Management
    • Define service templates to create sets of connected virtual machines, os images and applica tion packages
    • Compose operating system images and applications during service deployment
    • Scale out the number of virtual machines in a service
    • Service performance and health monitoring integrated with System Center Operations Manager
    • Decouple OS image and application updates through image-based servicing
    • Leverage powerful application virtualization technologies such as Server App-V

System Requirements

  • Supported Operating Systems:Windows 7 Enterprise;Windows 7 Professional;Windows 7 Ultimate;Windows Server 2008 R2;Windows Server 2008 R2 Datacenter;Windows Server 2008 R2 Enterprise
    • Windows Server 2008 R2 (full installation) Standard, Enterprise, Datacenter x64
    • Windows 7 Professional, Enterprise, Ultimate x32, x64
    • Windows Remote Management (WinRM) 2.0
    • Windows PowerShell 2.0
    • Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
    • Windows Automated Installation Kit (AIK) for Windows 7
    • SQL Server 2008 or SQL Server 2008 R2 Standard, Enterprise, and Datacenter
    • Windows Deployment Services (WDS) – (Version on Windows Server 2008 R2)
    • Windows Software Update Services (WSUS) 3.0 SP2 64bit

Download System Center Virtual Machine Manager 2012 Beta Evaluation HERE

Rollup 3 for Exchange Server 2010 Service Pack 1

exchange 2010

 

Microsoft releasd Update Rollup 3 for Exchange Server 2010 SP1 that  resolves the following issues that are described in the following Microsoft Knowledge Base (KB) articles:

2506998 A call is disconnected when transferring the call from the main auto attendant to an auto attendant that has a different language configured in an Exchange Server 2010 environmen

2497682 The store.exe process crashes when you try to unmount an active copy of a mailbox database that is hosted by a mailbox server in an Exchange Server 2010 SP1 environmen

2497669 A meeting request cannot be opened after you disable the "Display sender’s name on messages" option in the EMC on an Exchange Server 2010 server

2494798 Certain email messages cannot be downloaded when you log on to an Exchange Server 2010 mailbox by using an IMAP4 client applicatio’n

2494389 Unnecessary events are logged in the Application log when you run the "Test-EcpConnectivity" cmdlet in an Exchange Server 2010 environment

2489822 "The Mailbox you are trying to access isn’t currently available" error when you use OWA Premium to try to delete an item that is in a shared mailbox

2489713 Exchange Server 2010 SP1 supports the remote archive feature after an update changes Outlook cookies name

2489602 The "Get-FederationInformation" cmdlet cannot query federation information from an external Exchange organization in an Exchange Server 2010 environment

2487852 "You do not have sufficient permissions. This operation can only be performed by a manager of the group." error message when you try to change the "ManagedBy" attribute in an Exchange Server 2010 SP1 environment

2487501 The body of an email message is empty when you try to use an IMAP client application to read it in an Exchange Server 2010 environment

2484862 You cannot read an email message by using an IMAP client in an Exchange Server 2010 environment’

2482471 A content search fails in an IMAP client application that connects to an Exchange Server 2010 mailbox

2482103 It takes a long time to expand a distribution list by using EWS in an Exchange Server 2010 environment

2482100 You cannot create or update an inbox rule that specifies the "NoResponseNecessary" value by using EWS in an Exchange Server 2010 environment

2481283 Various issues occur after you use Outlook to sign and then forward an email message in an Exchange Server 2010 environment

2479875 The Microsoft Exchange Mailbox Replication Service service crashes when you run the "New-MailboxImportRequest" cmdlet to import a .pst file into a mailbox in an Exchange Server 2010 environment

2479227 Forwarding rule does not function and the EdgeTransport.exe process crashes on an Exchange Server 2010 server

2476973 Event ID 2168 is logged when you try to back up Exchange data from a DAG in an Exchange Server 2010 SP1 environment

2469341 Various issues occur after you forward a signed email message by using Outlook in online mode in an Exchange Server 2010 environment

2468514 OWA 2010 removes Calendar links that you add into multiple calendar groups by using Outlook 2010 calendar

2467565 You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated

2464564 You cannot change your password if the user name that you type in OWA is in UPN format when you enable Exchange Server 2010 SP1 Password Reset Tool

2463858 A request to join a distribution group does not contain the distribution group name in an Exchange Server 2010 SP1 environment

2463798 Users may experience a decrease in performance in Outlook or in OWA when you use IMAP4 to access the calendar folder in an Exchange Server 2010 SP1 environment

2458543 A memory leak occurs in the Exchange RPC Client Access service on Exchange Server 2010 servers

2458522 Entries disappear from a junk email blocked list or a junk email safe list after you install Exchange Server 2010 SP1

2457868 "HTTP Error 400 Bad Request" error message when you use OWA in Exchange Server 2010 SP1 to receive instant messages by using Internet Explorer 9

2457688 Error message when you try to add an external email address to the safe sender list in OWA in an Exchange Server 2010 SP1 environment

2457304 You receive a synchronization failed email message when you synchronize your mobile device by using ActiveSync on an Exchange Server 2010 mailbox

2451101 7BIT is not in quotation marks when you use the "FETCH (BODYSTRUCTURE)" command to request for a specific message in an Exchange Server 2010 environment

2447629 vent ID 4999 is logged when the Exchange Mail Submission Service crashes intermittently on an Exchange Server 2010 Mailbox server

2445121 memory leak occurs in the Microsoft.Exchange.Monitoring.exe process when you run the "Test-OwaConnectivity" cmdlet or the "Test-ActiveSyncConnectivity" cmdlet in the EMS on an Exchange Server 2010 server

2443688 Event ID 10003 and Event ID 4999 are logged when the EdgeTransport.exe process on an Exchange Server 2010 server crashes

2432494 You cannot view the mailbox database copies that are hosted on certain Mailbox servers by using the Exchange Management Console after you install Exchange Server 2010 SP1

2426952 You cannot remove a mailbox database copy from a database on an Exchange Server 2010 server

2424801 The Microsoft Exchange Service Host service on an Exchange Server 2010 server crashes

2423754 The recipient response status is incorrect after you add another user to an occurrence of a meeting request in an Exchange Server 2010 environment

2417084 A public folder disappears from the Public Folder Favorites list of an Exchange Server 2010 mailbox

2410571 A RBAC role assignee can unexpectedly change permissions of mailboxes that are outside the role assignment scope in an Exchange Server 2010 environment

2398431 Using Pipelining in SMTP to check email addresses does not work correctly when you disable tarpitting functionality on a Receive connector in an Exchange Server 2010 environment

2277649 You receive misleading information when you run the "New-TestCasConnectivityUser.ps1" script on an Exchange Server 2010 server

2009942 Folders take a long time to update when an Exchange Server 2010 user uses Outlook 2003 in online mode

You can download the update HERE

How to demote a Exchange 2007 CCR Cluster with Load balanced CAS/HUB Servers

I used the following steps to do this.

1. All public folders and system folders that are housed on the Exchange 2007 CCR Cluster computer must be replicated to another Exchange 2007/2010 computer that is in the site.

2. Verify the contents of the public folder store with the following Powershell commands
Get-PublicFolderStatistics -server <Exchange 2007_Server_Name> | fl | out-file d:\PFstat.txt

Get-PublicFolder -server < Exchange 2007_Server_Name > \ -recurse | fl | out-file d:\PFIPMSub.txt

Get-PublicFolder -server < Exchange 2007_Server_Name > \non_ipm_subtree -recurse | fl | out-file d:\PFNonIPMSub.txt.

3. Remove the replicas from the public folder store

MoveAllReplicas.ps1 -Server ccrclustername –NewServer newservername

4. Remove the public folder store

Remove–PublicFolderDatabase –Identity "Public_Folder_Store_Name"

5. Change the server that is responsible for generating the Offline Address Lists

Move-OfflineAddressBook –Identity OfflineAddressBookIdParameter -Server ServerIdParameter

6. Move the Routing Group Connectors by using the following command:

Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>

7. To modify any Send connectors that have the first Exchange 2007 server as the source transport server, run the following commands:

Get-SendConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-SendConnector -SourceTransportServers "<Second Exchange 2007 server>"

8.Important:
How to use the Exchange Server SP1 2007 Setup wizard to remove Exchange 2007

  1. Log on to the server from which you want to remove Exchange 2007.

  2. Open Control Panel, and then double-click Programs and Features.

  3. In Programs and Features, select Microsoft Exchange Server 2007, and then click Uninstall.

    If you click Change instead of Uninstall, you can add server roles, but you cannot remove server roles.

  4. In the Exchange Server 2007 SP1 Setup wizard, on the Exchange Maintenance Mode page, click Next.

  5. On the Server Role Selection page, clear all the server role check boxes, clear the Management Tools check box, and then click Next.

    By default, all server roles are selected. This indicates that no server roles will be removed. To remove a server role, you must clear the appropriate check box.

  6. On the Readiness Checks page, after the check completes, click Uninstall.

  7. On the Completion page, click Finish.

  8. (Optional) If you are removing Exchange from a Mailbox server, remove the Exchange database files (*.edb) and storage group log files (*.log).

    If you reinstall the Mailbox server role on this server, you must first remove the database and log files from the server.

  9. (Optional) Remove the setup log files that are located at %systemdrive%\ExchangeSetupLogs.

  10. (Optional) Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:

    • Microsoft-Server-ActiveSync
    • OAB
    • Owa

    When you remove Exchange 2007, neither IIS nor these virtual servers are removed

9.  First Remove the Passive Mailbox Node

10. Second the Primary Mailbox Role

11. Remove the CAS/HUB’s Role on the nodes
Important: NOT AT THE SAME TIME

12. Demote the Cluster

13. Demote the NLB Cluster

14. Remove the Servers from the domain

15. Shutdown the Servers

16. Take a cold bier when you are don with testing and everything works Winking smile

Exchange 2010 Free space within a Mailbox Database

In previous versions of Exchange Server there was a process called "online maintenance". This process ran at night and one of the tasks was to an online defragmentation to do within the database. The task was that the empty spaces are grouped together resulting in more efficient use of the Mailbox Database.

In Exchange 2010 has changed and there is a 24×7 online process. There is also the option of online, direct to see how much space is available within the databases with the Powershell command:

Get-MailboxDatabase –Status | fl Name,AvailableNewMailboxSpace

Output:

image

If we were to do an offline defragmentation on the Mailbox Database the mailbox database would be approximately a 90MB smaller.

This is on my test Exchange 2010 server with only a few mailboxes. In normal production enjoinment this will  be a lot more.

In Exchange 2010 you can you a online mailbox move. There fore you can
better create a new mailbox database en move all the mailboxes to the new mailbox database.
Then you have the same result with no down time.

Home folders renamed to My Documents

When you redirect users home folders to network share the folders are show as My Documents folder.

This is a bug in Windows 7 
http://support.microsoft.com/kb/947222

Solution:

Do not grant the Read permission to the administrator for the Desktop.ini files on the server. To do this, follow these steps:

Note If more than one Desktop.ini file exists, follow these steps for all the Desktop.ini files.

  1. Right-click the Desktop.ini file, click Properties, and then click the Security tab.
  2. In the Group or user names pane, click Administrators.
  3. Click to select the Deny check box for the Read permission.
  4. Click OK.

If you have 1000+ home folders this is not great thing to do Sad smile

Richard Willis created a nice powershell script that will do it for you Open-mouthed smile
You need only change the groupName to the group that you will give deny read permissions.
Save the script in de home folder where all the “My Documents” are and run the script.

The Script:
———————————————————————————————————–

$folders = Get-ChildItem | where-object {$_.psiscontainer};
foreach ($folder in $folders)
{
$desktopIni = Get-ChildItem $folder -Filter desktop.ini -Force
if ($desktopIni -ne $null)
{
$Acl = Get-Acl $desktopIni.FullName
$Ar = New-Object system.security.accesscontrol.filesystemaccessrule `
("groupName","Read","Deny")
$Acl.SetAccessRule($Ar)
Set-Acl $desktopIni.FullName $Acl
}
}

———————————————————————————————————-

After installing Rollup 1 for Exchange 2007 SP3 IMAP is now serving most text/plain parts as text/html

After installing Rollup 1 for Exchange 2007 SP3 IMAP is now serving most text/plain parts as text/html instead. I had some issue with a simple mail import tool that now imported all mail with html codes.

Before the rollup 1 they were previously multipart/alternative messages with both text/plain and text/html subparts.

Solution:
You can set in through in the GUI or using Powershell to set the value to 0 text only

ImapMessagesRetrievalMimeFormat:
0:Text Only
1:HTML Only
2:HTML and Alternative Text
3:Enriched Text Only
4:Enriched Text and Alternative Text
5:Best Body Format

Exchange Management Console:

  1. In the console tree, expand Server Configuration, and then click Client Access.

  2. In the work pane, click the POP3 and IMAP4 tab.

  3. In the work pane, select IMAP4 and then, in the result pane, click Properties.

  4. On the IMAP4 Properties page, click the Retrieval Settings tab.

  5. In the Message Retrieval pane, select a message format from the drop-down list under Message MIME format. I choies for 0

  6. Click Apply, and then click OK to save your changes.

Powershell:

Set-CASMailbox -Identity yourcasserverhere -PopMessagesRetrievalMimeFormat 0

Exchange 2010 Getting an overview of all ActiveSync devices in the Exchange-organization

If you want a list with al the pda’s that are connected to your Exchange Organization.

You can use the following Powershell command let.
Get-Mailbox –resultsize unlimited | Get-ActiveSyncDevice | fl userdisplayname,DeviceModel,Devicetype, DeviceUserAgent > c:\pdas.txt

image

Exchange 2010 SP1 Prerequisites

Some day’s ago Microsoft Releases Exchange 2010 SP1. When you install Exchange 2010 SP1 you need to install some hotfixes. The Exchange Team have made a nice over view witch hotfixes you need for the OS.

Hotfix Download Windows Server 2008 Windows Server 2008 R2 Windows 7 & Windows Vista
979744
A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application
MSDN
or Microsoft Connect
Windows6.0-KB979744-x64.msu (CBS: Vista/Win2K8) Windows6.1-KB979744-x64.msu (CBS: Win7/Win2K8 R2) N. A.
983440
An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2
Request from CSS Yes Yes N.A.
977624
AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista. Without this update, Active Directory Rights Management Services (AD RMS) features may stop working
Request from CSS using the “View and request hotfix downloads” link in the KBA | US-English Select the download for Windows Vista for the x64 platform. N.A. N.A.
979917
Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode
Request from CSS using the Hotfix Request Web Submission Form or by phone (no charge) Yes N. A. N. A.
973136,
FIX: ArgumentNullException exception error message when a .NET Framework 2.0 SP2-based application tries to process a response with zero-length content to an asynchronous ASP.NET Web service request: “Value cannot be null”.
Microsoft Connect Windows6.0-KB973136-x64.msu N.A. N. A.
977592
RPC over HTTP clients cannot connect to the Windows Server 2008 RPC over HTTP servers that have RPC load balancing enabled.
Request from CSS Select the download for Windows Vista (x64) N.A. N. A.
979099
An update is available to remove the application manifest expiry feature from AD RMS clients.
Download Center N. A. Windows6.1-KB979099-x64.msu N. A.
982867

WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1

MSDN N. A. Windows6.1-KB982867-v2-x64.msu (Win7) X86: Windows6.1-KB982867-v2-x86.msu (Win7)
x64: Windows6.1-KB982867-v2-x64.msu (Win7)
977020
FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.
Microsoft Connect N. A. N. A. x64: Windows6.1-KB977020-v2-x64.msu

X86: Windows6.1-KB977020-v2-x86.msu

Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBs. All these updates may become available on the Download Center, and also through Windows Update.

These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

The TechNet article Exchange 2010 Prerequisites is updated with the hotfixes and install the prerequisites required for your server version (the hotfixes are linked to in the above table).

You can use the Install the Windows Server 2008 SP2 operating system prerequisites on a Windows 2008 R2 server. Only you have to run the following powershell command: Import-Module ServerManager

Installed Exchange 2010 SP1 on a Windows 2008 R2 Server with problems. I feels that the MMC is faster. Tomorrow upgrading a DAG/NLB cluster to Exchange 2010 SP1.

Exchange 2010 Autodiscovery Issues

Two weeks ago a build my first production Exchange 2010 cluster. The Exchange 2010 web services are causing a lot of issues to people, and my self not any more.

Well, let us first list the directories that are used in the Exchange web service:

EWS is used for OOF, Scheduling assistance and free+busy Lookup.
OAB provides offline address book download services for client.
Autodiscover is used to provide users with autodiscover service.
EAS provides ActiveSync services to Windows Mobile based devices.
OWA provides outlook web access for users.
ECP provides Exchange control panel feature for Exchange 2010 users only.

Issues that might be resolved using the troubleshooting steps here:

You cannot set the OOF using outlook client, you receive the server not available error.
You cannot view free/busy information for other users.
You cannot use scheduling assistance, also you might receive not free/busy information data retrieved.
You cannot download Offline Address book errors.
You cannot use autodiscover externally.
Certificate mismatch error in autodiscover, users prompted to trust certificate in outlook 2007/2010.

First let us start by settings the right virtual directory configuration required for Exchange 2010 to work correctly:
Configure External and Internal URLs for OWS, ref: http://technet.microsoft.com/en-us/library/bb310763.aspx

You have to configure the internal URL to be the server name. In case you have multiple cas/hub servers configured in a NLB then can use the nlb cluster name for the internal url. 
External URL will be the URL used by users to access webmail e.g. https://webmail.wardvissers.nl/owa 

Configure the autodiscover internal URL, ref: http://technet.microsoft.com/en-us/library/bb201695.aspx

You will use the powershell cmdlet : Set-ClientAccessServer –Identity <CAS Server Name> -AutoDiscoverServiceInternalUri: <Internal URL>, this FQDN must match the URL included in the certificate. If you have NLB cluster then you put the internal name here like nlbek10.wardvissers.local

If you cannot use autodiscover.wardvissers.nl internally (you have a domain name of domain.local and you must use it), you will get a certificate miss match error, you will have to include the internal name in the SAN certificate if you purchase an external SAN certificate. 

You cannot set autodiscover external URL since outlook will try to access https://autodiscover.wardvissers.nl/autodiscover/autodiscover.xml, this behavior is by design and cannot be changed.

Best Practice: Use SAN Certificates

Depending on how you configure the service names in your Exchange deployment, your Exchange server may require a certificate that can represent multiple domain names. Although a wildcard certificate, such as one for *.wardvissers.nl, can resolve this problem, many customers are uncomfortable with the security implications of maintaining a certificate that can be used for any sub-domain. A more secure alternative is to list each of the required domains as SANs in the certificate. By default, this approach is used when certificate requests are generated by Exchange.

Best Practice: Use the Exchange Certificate Wizard to Request Certificates

There are many services in Exchange that use certificates. A common error when requesting certificates is to make the request without including the correct set of service names. The certificate request wizard in the Exchange Management Console will help you include the correct list of names in the certificate request. The wizard lets you specify which services the certificate has to work with and, based on the services selected, includes the names that you must have in the certificate so that it can be used with those services. Run the certificate wizard when you’ve deployed your initial set of Exchange 2010 servers and determined which host names to use for the different services for your deployment.

Which Names you must include when you use a third party SAN certificate, ref http://technet.microsoft.com/en-us/library/dd351044.aspx:
External:
webmail.wardvissers.nl
autodiscover.wardvissers.nl
legacy.wardvissers.nl (If you migrating from 2003 to 2010)
Internal:
autodiscover.wardvissers.local
legacy.wardvissers.local
nlbek10.wardvissers.local(Internal NLB CAS/HUB Cluster)
casarray.wardvissers.local(I use this address for the casarray. It has the same ip as the nlbek10)

MDT 2010 Importing automatically the right driver

Microsoft Deployment Toolkit 2010 has some nice improvements to handle drivers. I will describe how I like to manage drivers in MDT 2010.

Some time I wrote i article about how to get the Name & Model from a computer. This is very important when you want to import only the right drivers automatically.

First we have to build the ‘Out-of-Box Drivers’ folder structure and import drivers. I have subdirectories for each architecture, brand and model.  This is what my folder tree looks like:

MDT 2010 - Out-of-Box Drivers

However, you can build your own structure, as long as you respect the proper model & brand (make) name of the vendors.

Build Out-of-Box Drivers tree

To build up the folder structure you have to know the model name of your hardware. To retrieve the proper computer name execute at powershell command prompt: ‘Get-WmiObject -Class win32_computersystemproduct | fl Name,Model,UUID,Identifyingnumber,Vendor’, to get the exact name WMI queries to determine the computer model. In my case the computer name is “Latitude D830”.

Now that we have drivers imported in our Deployment Share, it’s time to move on.

1. DriverGroups

DriverGroups existed in MDT 2008 already, although the MDT Team added subdirectory support in MDT 2010.

At deployment phase MDT uses WMI to query the proper computer model and only the current model drivers will be injected. In order to get this working properly, you have to use the EXACT model name in your Out-of-Box Driver tree.

Inject the correct drivers in your Task Sequence

Add a new step in your Task Sequence to inject the correct drivers. MDT will query the computer name and inject the drivers which corresponds with the computer name from the Out-of-Box folder structure, right before applying the image at deployment.

MDT 2010 - Set Task Sequence Variable (Add Task) MDT 2010 - Set Task Sequence Variable (DriverGroup)

I use ‘DriverGroup_001’ as Task Sequence Variable, and Win7×64\%Make%\%Model% as value for my Windows 7 x64. You have to adapt this to your Out-of-Box tree.

MDT 2010 - Set Task Sequence Variable

As I use a DriverGroup I’ve disabled the ‘Inject Drivers’ task.

Customsettings.ini

As my Task Sequence handles everything, there isn’t anything needed here.

If you don’t like to use a new Task in your TS, you can add DriverGroup variables in customsettings.ini like this:

DriverGroup_001=%Make%\%Model%

DriverGroup_002=Printers

2. Selection Profiles

New in MDT 2010 are DriverSelectionProfiles. These are easy for new MDT admins, very straight forward and easy to use.

Overview:

MDT 2010 - Selection Profiles Overview

First you have to create a Profile (or use one of the default profiles):

MDT 2010 - Selection Profiles, select folders

You can even select Packages and Applications, use it for “bad drivers” aka driver setup packs.

Select what drivers you want to add to the profile;

MDT 2010 - Selection Profiles, add profile

After making the profiles you can use them in your Task Sequences. The default ‘Inject Drivers’ settings are on the left, the customized one on the right:

MDT 2010 - Selection Profiles, task sequence MDT 2010 - Selection Profiles, task sequence

You can add  Selection Profiles for drivers/packages or whatever you want. Just add an extra step in your task sequence like above.

Customsettings.ini

As with DriverGroups you can choose to handle the DriverSelectionProfile in customsettings.ini or in your TS.

Example:

DriverSelectionProfile=Dell Latitude D520 x64

Translate »