I just finished trying out the same demo that was presented in the TechEd session and it worked pretty well. It took what seemed quite a while, but there are numerous things that could have contributed to that.
The only major thing that didn't work was the default login provider reverted from the Novell client back to the Windows client. I'm thinking I could possibly use the "setupcomplete.cmd" script to ensure that the proper login provider is set though. Other than that everything else seemed to have worked outside of some small issues (screen resolution reverted back to 1024x768, logon background reverted to the default multi-color background). Now, I'm really interested in the "Provisioning Packages" that WICD can create. Depending on how extensive those can be I'm picturing a lot of potential with them. Mike From: [email protected] [mailto:[email protected]] On Behalf Of Keith Garner (Hotmail) Sent: Thursday, October 30, 2014 3:29 PM To: [email protected] Subject: RE: [MDT-OSD] RE: Whats the future of MDT and Windows 10 ? I think the Microsoft Windows Product Groups have finally woken up to the fact that Wipe and Reload (aka Refresh) is hard, error prone, and incomplete. I've been largely disappointed with the alternatives. For example: Upgrade from Windows XP to Windows 7? Too bad! Use an MDT/SCCM Task sequence to save your settings and data via usmt, reinstall the os, and restore from USMT, install all new apps from scratch, and hope you remembered to include the correct drivers. If we can "Upgrade" from Windows 7,8,or 8.1 to Windows 10, initiated from a MDT or SCCM Task Sequence, that would be fantastic! You won't be able to use your custom *.wim image, but Windows Setup will migrate all Files , Settings, Drivers *and* applications to the new OS. My personal view? In the near future ( 1-3 years ) think of maintaining two OS deployment systems: 1. Your existing MDT/SCCM-OSD deployment system for NewComputer scenarios. With your Custom-image. 2. The incremental upgrade scenario, OS updates distributed via WU, WSUS and/or SCCM. a. Sometimes the OS updates will be as small as a *.msu package. b. Sometimes the OS Upgrade will be a larger *.wim, with App, Data, & Settings handled by Windows Setup. -k From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Thursday, October 30, 2014 10:56 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Whats the future of MDT and Windows 10 ? Seesm like MS is heading towards a model where we don't deploy the actual OS anymore. With Windows 10 and beyond the OS will be there and we will just configure it. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Thursday, October 30, 2014 12:43 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: Whats the future of MDT and Windows 10 ? There was a TEE session that covered this at a high level: http://t.co/2GkjIE6XRA The only real major change is that they will support in place upgrades within ConfigMgr to Win 10 and have a task sequence type for this now. MDT is not going away anytime soon although they didn't give any real details. J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Bain.John Sent: Thursday, October 30, 2014 12:36 PM To: '[email protected]' Subject: [MDT-OSD] Whats the future of MDT and Windows 10 ? Hey Everyone, Has anyone heard what MS plans to use for deploying Windows 10? Will there be more emphasis on VHDs ? What changes will Windows 10 bring to deployment scenarios ? Just random thought really John ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
