Hi, Yes. Check out www.hurryupandwait.io. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: 24 December 2016 00:35 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Does that wwork with vhdx files? -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Friday, December 23, 2016 4:04 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Hi, That's not the case. Check out Packer, that is the way I create my Windows images. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: 23 December 2016 20:12 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Where we need to get is the level of scripting that NanoServer has in terms of installing the OS; with that, you don't even see an interface nor do you first have to capture an image from an existing one. What gets me about the current method of automation is the fact that in order to get an image ... unless I am misunderstanding something, you have to install the OS manually, walk through the steps by hand, and then finally capture an image, and it's a painin the butt and a half to get the automation set up where the image capture is taken care of for you ... in other words, if you don't have a file server setup beforehand, you're sort of up a creek. There should be some way to walk through that via powerShell onto a VHDX file via the .WIM alone. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Friday, December 23, 2016 3:02 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update You could argue that automated testing would fix this, My Chef automation is backed up by automated test cases which can be tested without any issues. I see though what you are saying, and that getting the automated testing working is a bit of a step, but it really is a game changer in terms of moving forward. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: 23 December 2016 17:31 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update True ... but then the problem occurs that if we can't see what our automation is doing ... how to ensure that we do it right the first time? For testing automation, at least, audio and speech needs to exist so that a sighted individual doesn't have to sit through dozens of testing phases. I don't need my mother standing there confused for 20 minutes while I run experiments in the lab. LOL. If you want to go that way ... then I propose a PowerShell based way of capturing images ... so that one doesn't have to boot into WinPE for that ... for unless audio is present, the same old horn comes around again. I am interested in this part of the setup in particular because I wanted to try automation on my own projects as well. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Friday, December 23, 2016 12:04 PM To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Subject: Re: [Blind-sysadmins] Windows 10 creators update Hi, I agree with you guys about having a simple audio toggle for the OOB, but believe that in the future we will be seeing automation only on the server side. That is, we won't be doing manual installs of Windows server at all. I think that automation in current times is the only real way we as blind sysadmins can really compete with others as it puts us on a level playing field with other sysadmins as we use the same technology and ways of working. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart via Blind-sysadmins Sent: 23 December 2016 05:01 To: Blind sysadmins list <blind-sysadmins@lists.hodgsonfamily.org> Cc: Ryan Shugart <ryshugar@microsoft.com> Subject: Re: [Blind-sysadmins] Windows 10 creators update Hi Katherine: I just wanted to update you on your question, I did reach out to some of the Narrator team and asked about server SKUs. The short answer is yes, the releases of Windows Server 2016 based on the creater's update of Windows 10 will have the talking Windows PE based install. I still believe that as soon as you boot into the actual Windows Server OS for the out of box experience, the Windows Audio service will be disabled and you won't have speech for that part of setup. I did raise this feedback so we'll see how far it goes, but to be honest in an enterprise environment, most companies have automated ways to set their servers up. Many servers don't even have sound cards, although I do understand that could be worked around easily with a USB headset, so that argument doesn't go too far. Most of the people I know either used an automated setup to install Windows Server, or they'd be using something like ILO on HP servers to install the server remotely anyway. I'm not saying the feedback and issue isn't important as it is, just saying that its not common to do an interactive setup of Windows Server at the server console. Ryan -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Katherine Moss Sent: Saturday, December 17, 2016 2:32 PM To: 'blind-sysadmins@lists.hodgsonfamily.org' <blind-sysadmins@lists.hodgsonfamily.org> Subject: [Blind-sysadmins] Windows 10 creators update Hi all, Can anyone speak on whether the supposed integration of Narrator with the installation/setup/PE process will also extend to server operating systems? Nothing about said integration was mentioned in the blog post, though you would think that something could be done about it ... if one side of an interface is accessible, then all sides of it ought to be. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.hodgsonfamily.org%2Flistinfo%2Fblind-sysadmins&data=02%7C01%7Cryshugar%40microsoft.com%7C7af675a1fae444128c3608d426bbd74d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636176035589573968&sdata=gaRsK9BLoN9ilJFEqFm%2BxWmlcNsaBne1uyFy%2FexXtcE%3D&reserved=0 _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org https://lists.hodgsonfamily.org/listinfo/blind-sysadmins