Anonymous_User Absent Member.
Absent Member.
868 views

Build Windows 10 v1703

Hi,

Does someone tried to create an image from Windows 10 v1703 ?

With Windows 10 v1511 or v1607, my unattend xml file was working fine but
with v1703, it looks like the Autologon option isn't tooked in consideration
for the second autologon.

Thanks for help.

Normand

Labels (2)
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: Build Windows 10 v1703

This would be a MS Bug as far as I can tell as ZCM is not involved in any of that....

Luckily for you, lost of folks feel your pain.....

https://social.technet.microsoft.com/Forums/en-US/c59091a7-0fae-4dca-8baa-193c0906efe1/mdt-8443-w10ent-1703-auto-login-and-wsus-issue?forum=mdt
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Build Windows 10 v1703

Craig,

I just saw it before you answered the post.

Thanks for help.

Normand

"CRAIGDWILSON" a écrit dans le message de groupe de discussion :
CRAIGDWILSON.7y11kn@no-mx.forums.microfocus.com...


This would be a MS Bug as far as I can tell as ZCM is not involved in
any of that....

Luckily for you, lost of folks feel your pain.....

https://social.technet.microsoft.com/Forums/en-US/c59091a7-0fae-4dca-8baa-193c0906efe1/mdt-8443-w10ent-1703-auto-login-and-wsus-issue?forum=mdt


--
--
Any Opinions, Thoughts, Solutions, or Blog Entries are my own and may or
may not be shared by Novell or any Sane Person
Please Use at your Own Risk.

Blog - https://forums.novell.com/blog.php/5830-CRAIGDWILSON

https://ideas.microfocus.com/mfi/novell-zcm

Want to Turbo charge your apps and put an end to compatability issues?
https://www.microfocus.com/products/zenworks/desktop-containers
------------------------------------------------------------------------
CRAIGDWILSON's Profile: https://forums.novell.com/member.php?userid=5830
View this thread: https://forums.novell.com/showthread.php?t=503572

0 Likes
shaunpond Absent Member.
Absent Member.

Re: Build Windows 10 v1703

Craigdwilson,

yes, it's something we found during testing for support for the new
version of our Imaging Toolkit product - we've had to make coding
changes...

--

Shaun Pond (now working for ENGL)
reminted as a Knowledge Professional


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Build Windows 10 v1703

Shaun & Craig,

I resolved the issue by adding registry keys in a script after 1 autologon:

$RegPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon"
Set-ItemProperty $RegPath "AutoAdminLogon" -Value "1" -type String
Set-ItemProperty $RegPath "DefaultPassword" -Value "password" -type String

And by removing those keys in another script after the second logon:

Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon" -Name "AutoAdminLogon"
Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\Winlogon" -Name "DefaultPassword"

And now it's working fine.

Normand



"Shaun Pond" a écrit dans le message de groupe de discussion :
VA.00011130.09af5f8b@no-mx.forums.microfocus.com...

Craigdwilson,

yes, it's something we found during testing for support for the new
version of our Imaging Toolkit product - we've had to make coding
changes...

--

Shaun Pond (now working for ENGL)
reminted as a Knowledge Professional

0 Likes
shaunpond Absent Member.
Absent Member.

Re: Build Windows 10 v1703

Normand,

pretty sure that's the sort of thing we're doing as well, but I've not
been involved in the changes...

--

Shaun Pond (now working for ENGL)
reminted as a Knowledge Professional


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.