OSD slides from SCUGSE event, January 22, 2013

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
3 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
9 years ago

The scratchspace size are set correctly for the boot images but the Console UI is not correctly reflecting this.

The MDT boot image wizard is modifying the template (Winpe.wim), the ConfigMgr console is modiying the winpe..wim, which is based on the winpe.wim template.

/ Johan

Thomas
Thomas
9 years ago

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_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon]"DefaultUserName"="someuser""DefaultDomainName"="somedomain""AutoAdminLogon"="1""DefaultPassword"="somepassword""DontDisplayLastUserName"="0" When I use the image created using MDT,… Read more »

Bjurte
Bjurte
9 years ago

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, http://www.balm.se/?p=43

Regards
Björn


>