There's really not much to say about this Jump Start other than the fact that I already have MDT 2013 Update 1 for deploying Windows 10 like I'm already doing right now after having sufficient solutions. I had already anticipated the newest deployment tools like the Windows 10 ADK which should have Windows 10 PE as well as the final version of MDT 2013 Update 1 which at that time, it still had yet to be finalized while Windows 10 ADK was already finalized. New to Windows 10 ADK is the Windows Imaging and Configuration Designer and somehow, it is like Windows System Image Manager or something where you can customize the answer file component by component which can be useful for automatic specification of the information during Windows Setup. Also, the existing versions of today's System Center Configuration Manager are already supporting Windows 10 deployment via some updates provided that you have the latest service packs and cumulative updates needed for that.
Unfortunately, at that time, other things still had yet to be finalized as well such as RSAT for Windows 10, Windows 10 IOT or something and of course, Windows Server 10 which is now at Technical Preview 3. That server variant may be based on Windows 10 but at a later build and especially when it has all the latest features of Windows 10 RTM like the new login screen, new wallpapers, new event sounds, etc. However, there are still older stuffs intact when I checked out the Windows event sounds from default sound scheme in Sounds properties. I could have called that tab, Event Sound tab because when a message box occurs, there should be an event sound for instance. From there, not all event sounds are new in Windows 10 as if even at the RTM stage, they still have yet to work on in adding and improving features in Windows 10 as if they're milking it for years and especially that there's a post-RTM build for insiders.
Other stuffs I saw included the migration of the user settings between
Windows 8.1 and 10 and it was why the prototype Windows 10 wallpaper was
migrated along when I installed Windows 8.1 trial the last time
probably due to the fact that one of the Insider Preview builds was
unbootable on various physical machines unless some options in the BIOS
were turned off. However, its later build solved those reboot-loop
problems as tested on booting up from that build's setup DVD in which I
was able to see the setup screen.
Deployment Progress
The Enterprise edition of Windows 10 has full security opt-out options unlike the other editions of Windows 10 in which some of the features cannot be disabled. Also, the Pro and Home editions downloaded from Microsoft via Media Creation Tool or whatever cannot be imported straight to MDT or SCCM for deployment. Regardless of prototype or final stage, it's not going to work that way. I already have the reference image of the Enterprise Edition evaluation in the MDT with various things configured with the help of the external sources found on the net. The next phase will be to do the same thing for the server variant as well as Windows 8.1 with Update.
The recent problem I have is regarding the domain user account policy that should be applied to the clients in the domain. How do I apply the Windows 8.1 and 10 policies to those accounts including the new ones?
Networking Rant
I still have some networking rants in my head against various Microsoft sub-domains and websites including Microsoft Virtual Academy as their networks are unspeakably sensitive compared to other websites which are working quite well. Maybe those networks running those sites are to blame for technical stupidity acts and I don't know what the hell are those setting up and maintaining those networks are doing. Scold them, or maybe those US ISPs! They don't know what the hell are they doing that affects the Microsoft networks in the US a lot that made me freak out over networking misbehavior. And why are some of the video players on MVA still using Adobe Flash. Are they lazy or something? Why isn't the MVA site using HTML5-only media players on all courses and Jump Starts? Maybe my feedback two years ago wasn't quite enough? I don't even know if the whole MVA website works well in Microsoft Edge. Lastly, if this is the way those networks I mentioned continued to work like that like a bunch of robotic idiots bought or designed by idiots from some idiotic companies, that will cause another major layoff to happen one day.
Pages
Showing posts with label Microsoft Deployment Toolkit. Show all posts
Showing posts with label Microsoft Deployment Toolkit. Show all posts
Sunday, August 23, 2015
Sunday, August 2, 2015
Windows 10 RTM opinion
This one's a big story for me but some of the controversies are still intact for Windows 10 as if retarded people may think that we with security concerns don't care for anything else which is one of the stupid thoughts we know of. Even after Windows 10 had gone to RTM stage, there are some articles regarding Windows 10 security concerns but there are already options you can disable for privacy reasons as if Microsoft has done things right with Windows 10 security. However, it is not the same for other features of Windows 10 as well like bandwidth being overused without people's consent, updates are made compulsory like there's no way to turn them off in Home edition which may result in buggy updates breaking Windows 10 systems and the list goes on. There are already solutions on the way that put an end to those problems but even then, the rest of the technology has yet to be finalized for full support of Windows 10.
Through security concern of mine, I had decided to try deploying Windows 10 RTM but it backfired on me as something made the WIM format look unknown to MDT 2013 Update 1 preview so I couldn't import anything there. I don't know if the Update 1 will be finalized with that bolded problem solved for smooth deployment. The official announcement had already stated that the finalization of Update 1 is already on the way for release sometime this month. I don't know if the import works for Enterprise edition of Windows 10 RTM only or what. If that's the case, it's a controversial deployment of Windows 10 for OEMs unless they find other deployment solutions that will help them get through. The actual intention for image customization was to remove certain modern apps as well as to install some security-related ones before Sysprep but I guess that making use of the custom ISO file containing all those things needed for customization was what I missed out in the first place.
Needless to say, I already Syspreped the VM running Windows 10 RTM Pro with partial customization as the network and USB access are obviously disabled in Audit Mode but I don't know if I can move on to the next phase which is image capture
Through security concern of mine, I had decided to try deploying Windows 10 RTM but it backfired on me as something made the WIM format look unknown to MDT 2013 Update 1 preview so I couldn't import anything there. I don't know if the Update 1 will be finalized with that bolded problem solved for smooth deployment. The official announcement had already stated that the finalization of Update 1 is already on the way for release sometime this month. I don't know if the import works for Enterprise edition of Windows 10 RTM only or what. If that's the case, it's a controversial deployment of Windows 10 for OEMs unless they find other deployment solutions that will help them get through. The actual intention for image customization was to remove certain modern apps as well as to install some security-related ones before Sysprep but I guess that making use of the custom ISO file containing all those things needed for customization was what I missed out in the first place.
Needless to say, I already Syspreped the VM running Windows 10 RTM Pro with partial customization as the network and USB access are obviously disabled in Audit Mode but I don't know if I can move on to the next phase which is image capture
Thursday, March 13, 2014
Windows 8.1 Deployment Jump Start
OK, I did have the prerequisites for this Jump Start like I already had the knowledge and experience of Windows Deployment all along through the MVA courses I took. The tools demonstrated so far were System Center Configuration Manager and MDT but it might seem that System Center Configuration Manager was starting to get more complicated to use and especially when you need to correct the task sequences for the sake of Replacement, Refresh and Bare Metal.
Also, the difference between MDT and System Center Configuration Manager was that when the computer boots up to Windows PE through the network, the drivers and other stuffs were loaded into RAM for MDT as if you needed more RAM for that compared to System Center Configuration Manager. The cool thing about SCCM was that you can use the Remote Desktop feature inside it to remotely gain access to the machine you're monitoring as well as to check the report of how many MDT-like tasks have been completed so far. Not to mention that you can make custom UDI Wizard for SCCM but then, that will not be called Zero Touch Install all along.
Lastly, there were way too many people attending this Jump Start including me that certain users were ignored when they asked the questions. Perhaps it was better for me to continue tweeting things about the Jump starts and I got some reply as a result.
Also, the difference between MDT and System Center Configuration Manager was that when the computer boots up to Windows PE through the network, the drivers and other stuffs were loaded into RAM for MDT as if you needed more RAM for that compared to System Center Configuration Manager. The cool thing about SCCM was that you can use the Remote Desktop feature inside it to remotely gain access to the machine you're monitoring as well as to check the report of how many MDT-like tasks have been completed so far. Not to mention that you can make custom UDI Wizard for SCCM but then, that will not be called Zero Touch Install all along.
Lastly, there were way too many people attending this Jump Start including me that certain users were ignored when they asked the questions. Perhaps it was better for me to continue tweeting things about the Jump starts and I got some reply as a result.
Subscribe to:
Posts (Atom)