Re: OSD slides from #scugse event January 22, 2013

Hi Johan,

During your presentation at the SCUG.SE event you recommended to extend the Windows PE scratch space when creating a MDT Boot Image. I may have found a bug in the wizard (or other process) because the value that you choose in the wizard isn't applied, or at least not shown when you look at the properties on the newly created Boot image. Is that something you have seen also?

This is a link to a page with some screen shots to illustrate what I mean, www.balm.se/?p=43

Regards
Björn

Re: OSD slides from #scugse event January 22, 2013

Hi Johan :-)
I got a question regarding AutoLogon.
I recently created my reference image using MDT (I've been using SCCM for this in the past) and I must say everything works like a charm, except one thing - AutoLogon.
In my production environment, I have a few builds which require AutoLogon, this is production Pc's and Info screens which is completely locked down. When using the image created using SCCM this is no problem, I got a step in my TS which import the following registry settings:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"DefaultUserName"="someuser"
"DefaultDomainName"="somedomain"
"AutoAdminLogon"="1"
"DefaultPassword"="somepassword"
"DontDisplayLastUserName"="0"

When I use the image created using MDT, it appears that no matter how I add the registry keys they are overwritten? Do you have a workaround for this? I've found this guide scottmhowell.wordpress.com/2012/08/10/mdt-2010-and-autologon/ which describes the exact same problem, however I would prefer a more supported solution.

Thanks in advance... :-)

Best regards,
Thomas