I’ve been quite busy lately so I’ll try to be quick… I would like to share my discoveries on MDT 2012 and the information I gathered while I was migrating from MDT 2010.
- Mikael Nystrom’s step by step on how to update BIOS in MDT still works perfectly.
- Andrew Barnes’ how to integrate BGInfo into WinPE still works, and even better, MDT 2012 comes with a 64-bit version of BGInfo (located at %deploymentshare%\Tools\x64).
- It is no longer needed to have a custom pane to set local administrators in MDT 2012. Instead use the “SkipAdminAccounts=NO” property in CustomSettings.ini. Please note that the administrators accounts page only appears if you selected “Join a domain” as I mention on the TechNet Forums.
- Thanks to Michael Niehaus, DaRT integration is now fully supported in MDT 2012. I talked about this earlier but it’s always good to reiterate the benefits of software assurance.
- A very interesting new feature of MDT 2012 is monitoring. It can be enabled in a few simple steps: Navigate to your deployment share properties, go to the last tab called “Monitoring”, check the box called “Enable monitoring for this deployment share”. Then click OK. It should work right away… A good way to check is to look at your CustomSettings.ini for a new line called “EventService=http://myserver.corp/contoso.com“. Is you run into issues there is always this good troubleshooting article. Used in conjonction with DaRT, you can remotely control deployments from a central location.
- Another feature that might not be actually that new but still useful is the “SLSHARE=” property. It allows you to set a network share where the logs are written during the deployment. This is particularly useful when your helpdesk people forget to capture logs if a deployment fails. A good security practice it to set a sticky bit, using the user directory technique on that particular folder since logs may contain sensitive information.
- You are now able to use only one (32-bit) boot image to initiate both 32-bit and 64-bit deployments. A word of caution, though, if you need to use DaRT to repair an install you will need to boot the appropriate architecture.
After installing SCCM I noticed that IIS was not populated with the different websites needed to run ConfigMgr properly.
I took me hours to figure out until I found the ConfigMgr Toolkit
. Run the MP Troubleshooter, it will solve the issues.
Of course MS could fix that easily but that must be too much to ask for.
I came across the need to deploy iTunes using MDT (2010 or 2012). Unfortunately, there is no way to run the usual setup file with switches.
The key is to expand the installer (using 7-zip
) and then create hidden applications for each component (that also allows you to prevent Bonjour or Apple Software update from installing…).
Install the MSI files in this order:
Using this command: msiexec /i XXX.msi /qb REBOOT=ReallySuppress
(where xxx is the msi filename, of course)
It also works for the 64-bit version. Every time there is an update of iTunes, simply overwrite the files on your network share.
Sometimes when Outlook changes network contexts (i.e. from wired to wireless), it triggers an annoying authentication popup. There’s a way around:
- Open Outlook.
- Go to “Tools” > “Account Settings”.
- Double click on your account.
- At the bottom right, click on “More Settings…”.
- Click on the “Connection” tab.
- Under “Outlook Anywhere”, click on “Exchange Proxy Settings”.
- Uncheck the “On slow networks, connect using HTTP first, then connect using TCP/IP”.
Just a useful tip from the top of my head. If you want to migrate Outlook settings without having to reconfigure accounts, delivery options and PST locations, here is the registry key you need to export:
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
* If you’re migrating from XP to a next-gen OS (Vista or 7), you’ll get some error messages because C:\Documents and Setting\User\Local Settings\Application Data is now C:\Users\User\AppData\Local make sure you put the PST files in the right place and simply browse to their location when asked.
There we are, finally… Let’s talk about the installation of Microsoft Deployment Toolkit 2010.
First of all, I have to say that I’ve been blasted by this product. It’s been the first time in a long time since I really appreciated using a Microsoft product… Let’s leave the troll aside and proceed with the installation steps.
They obviously need to be installed in that order.
- On your server, open Server Manager then scroll down to Roles. Click Add Roles then find Windows Deployment Services. Restart your server if prompted to do so.
- If not already installed, download and install MSXML 6.0 or better.
- Download and install WAIK using the link above. It will be used to manage settings inside the images by generating catalogs and XML configuration files. WAIK is also some kind of WYSIWYG editor for the aforementioned XML files.
- Finally, install MDT 2010.
This process should be straightforward if you have installed the utilities in this order. Please note that MDT 2010 doesn’t require WDS to install or run since WDS acts only as a transport for the images. MDT can be run off CDs or DVDs instead of PXE, but that’s not really what you want to do, right?
Sorry, I’ve been quite silent recently but I’m currently writing a pretty exhaustive guide to Microsoft Deployment Toolkit 2010 (MDT 2010).
Double clicking on an Excel file does not open it. Instead Excel opens and displays a blank workbook. However, if you minimize Excel, it will immediately maximise itself and display the file you originally tried to open.
The solution is really weird: You can stop this annoying behavior by adding an Add-in, like this:
Excel options >Add-Ins > Manage: Excel Add-Ins > Euro Currency tools.