Written by Me and a couple of colleagues has established MSitPros.com, so all my future blog post will be posted there.
Drop on by: http://msitpros.com
This blog will still be active as an archive, but I will not make any new posts here.
New posts to a new place. MSitPros here I Come
Windows Thin PC aka WinTPC
Microsoft has just launched a beta program at connect for Windows Thin Pc. Its intention is to be able to install a light weight operating system to old machines and elevate VDI and terminal services. I just had to install it and test it out. And guess what, it looks great. See screen shoots below.
Cannot add or remove windows features. This is disabled.
Uses 2,67 GB of space after it is installed. (that’s small)
More info on thin pc can be found here:
http://www.microsoft.com/windows/enterprise/solutions/virtualization/products/thinpc.aspx
Problems with Language packs with Windows 7 Service Pack 1
I recently had some problems injecting language packs offline into a Windows 7 Service pack 1 image file. After a lot of troubleshooting I realized that when Service pack 1 was released there were also released Service pack 1 versions of the language packs (dough!). The language packs can be downloaded from licensing.microsoft.com.
USMT and Office 2010 settings
There has finally been released a hotfix to make USMT handle office 2010 settings.
http://support.microsoft.com/kb/2023591
Deploy Office 2010 with Different languages
As seen on my previous post http://www.moe.am/index.php/2010/08/deploy-office-2010-with-integrated-language-packs/ I showed how to integrate language packs into one set of installation files for office.
In that post I also showed you how to put a config.xml in the root of the directory together with the setup.exe. Inside that XML file we added all the languages we wanted to add. In many cases you may want to only deploy a subset of languages. So how do we do that? This is easy. All you have to do is to create a XML file for what type of languages you want. Let’s say we want Spanish and English only. Then I have chosen to create a XML file called Spanish.xml and it looks like this:
<Configuration Product="ProPlus"> <Display Level="none" CompletionNotice="no" SuppressModal="Yes" AcceptEula="Yes" /> <AddLanguage Id="es-es" ShellTransform="yes"/> <AddLanguage Id="en-us" /> <OptionState Id="OfficeMUI" State="Local" Children="force" /> </Configuration>
Then when I deploy office I just use this command to apply this config:
setup.exe /config Spanish.xml
If you also want to apply office customizations you can do this after the installation just by running the MSP package that you have created using setup.exe /admin
Good luck!
Windows 7 Service pack 1 is supported in SCCM
This is now supported. All you need is this hotfix:
http://support.microsoft.com/kb/2489044/en-us
Custom Error Codes for Configuration Manager 2007
Just stumbled over this nice page on technet:
http://technet.microsoft.com/en-us/library/bb632794.aspx
It shows a list of error messages from System Center Configuration Manager and what they mean. Great list!
TimeZoneName, InputLocale and Language Tag
If you have ever tried to find a good documentation to what the TimeZoneNames should be when you are trying to deploy to different time zones, you can just have a look in the registry on a Windows 7 computer under the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones
Here you will find the complete list with the correct TimeZoneNames that you need for MDT.
And the Inputlocale you can find under this following registry path:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts
If you also need the language tag ID you can find a list here:
http://technet.microsoft.com/en-us/library/cc179219.aspx
And as a bonus here is a link to where you can find default values for language packs:
http://technet.microsoft.com/en-us/library/cc766191(v=ws.10).aspx
Thank you for voting!
Having trouble generating catalog file for Windows 7 X86
I am guessing you are trying to edit unattend.xml file in WAIK. And in order to do that you have to generate a catalog file. In order to generate a catalog file to an X86 WIM/OS you have to do it on a computer/server with X86 OS with WAIK installed. After you have generated the catalog file you can copy it to your X64 server and do the editing from there.
Best Practices for maintaining office 2010
Microsoft has release a best practice document in regards of maintaining Office 2010 installations. Great reading
http://technet.microsoft.com/en-us/library/cc982159.aspx