Planehazza

Bumping an old thread. Does anyone know in MoviePus X6 if there's a way via a file or registry to change the location of the Folders in the Options area? Can't see anything when scanning through the program and appdata directories, nor can I see anything via regedit.

Just a bit of an excuse to get away from it for 5 mins, as it's an awfully dull and monotonous task, but how do you guys bulk update storage/home drive quotas with FSRM? We have auto apply quotas which is great for applying the 200MB Year 7 limit to all child folders of the 2017 parent folder. Go up to year 9, they get 400MB; great. However, from Year 9 onwards, they can do photography. Our photography quota is 15GB. So currently, I have to go through the accounts (~4000 of them) to manually apply a quota. I have about 60 kids that need this quota. Filtering to the year parent folder makes it a lot easier, but I still have click on them and apply the quota one by one. Is there a simple way to bulk update them? I've read up and it doesn't seem natively doable with powershell, and by coding knowledge and skills are very low. It's a shame I can't apply quota templates based on AD groups. I could create subfolders in the 2015, 2014,... groups called photography and move their home areas into there, update their home drive maps, and reapply a an auto quota to \students\2015\photography, but it's a lot of extra work and it adds confusion about H drive location.

I've had this same issue myself; if it has partitions already the WillWipeDisk fails. If you manually delete them all, reboot, then run WinPE answer file again, suddenly the partitions are there and install can commence. To get past this, I cheated and gave up entirely on using the WDSUnattend.xml to do the disk setup. Intstead, I wrote a batch file and a txt file with diskpart commands to erase and partition disk 0. It's an extra step though and it does require you to have to press shift f10 to open up a command prompt and run the batch file. Ideally I want to use WDS with MDT to automate everything as I'm of the opinion now that WDS on its own is just not clever/powerful enough. Is your answer file working at all? Do your locale/language/login to WDS settings work? EDIT: I see they do.

We're currently using WDS on its own, but I want to move to WDS/MDT. We're currently buidling department/HW based images and it's a lot of a extra work. Once our Summer W10 is done, I'll be moving to MDT and pushing out raw W10 media for sure.

EDIT. This wouldn't fooking work either, and looking at this, it never will: https://slightlyovercomplicated.com/2016/11/07/windows-pe-startup-sequence-explained/ So instead, I've injected a simple bat file to the PE image so that we just have to press Shift-F10 and run 1.bat which works like above but without wpeinit, obviously. A bit of a hack, but anything to speed up the process is a win. I've told the team we're moving to MDT once this is all. A slightly unrelated issue... I took a copy of the boot.wim from the winPE image as backup; next thing I know I've two duplicate boot images appearing in WDS. I moved the backup elsewhere and the duplicate has disappeared from WDS, but it still appears in windows boot manager when we boot the clients to the NIC. Is there a way to edit the boot manager manually?

Have given up on using the answer file to do my drives entirely. Have modified startnet.cmd to run 'diskpart /s diskpart script'. Now, this isn't running. If I shift-F10 and manually trun startnet.cmd, it runs through and sorts my drive/partitions perfectly. Why isn't startnet.cmd running, and at what point does it actually run? My startnet.cmd file:

%20 removed, no change. Addtional 300MB partition added, off to test...

The InstallImage isn't used anywhere on our setup, as I want to be able to select the image to install. I've set it up so that a thin WDSunattend preps the drive, logs in to the WDS server and prompts us to select the image. I then have an ImageUnattend tied to the images to do the specialise/oobe etc. stuff. I'll try removing the %20s and then try adding a second partition.

yeah I've learned not to entirely trust and rely on the validation. What reports as 100% good isn't always, especially in the M$ world ha. Regarding extra partitions, I'll give that a go. If I cannot get this 'willwipedisk' to work, I'll just use a script to run the commands via diskpart. It did the trick when I hit shift f10 and typed the following, line by line: Can annoyone recommend the best package to insert into the WinPE pass to run said Diskpart.bat? Also, I assume I can safely mount the boot.wim image and insert the batch file into it as I would with a normal install image? Again, though that's only creating one partition on disk 0, yet the image continues to install just fine. It seems I'm having the same problem as many on the Internet; if the disk is simple, ie one partition, it continues and installs just fine. If there are >1 partitions, it says it's cannot install on the prepared partition. Reboot, and then attempt a second time (without doing any partition or drive stuff) and it installs just fine...

Urgh, I've read and read and read, but I cannot my x64 WDSUnattend.XML to work properly. I've managed to get it all automated except for the DiskConfiguration part. It still prompts to me to wipe and create partitions. If I do, installation fails saying it can't install to the prepared partition. I force reboot, do it again and I still get prompted to select the disk, but installation proceeds. What have I balls'd up for W10 LTSB deployment with my WDSUnattend (applied to x64 architecture on the en-US 0809:00000809 en-GB en-US en-GB 0 true 1 Primary true true false NTFS OS C 1 1 OnError Kenton ******** WDSService 0 1 Any help would be greatly appreciated. Apologies for the formatting getting messed up...

We're a big school, with ~2000 students and ~350 staff. We did an audit and of the ~350 bits of software we have only a handful came back as 'can be got rid of'. I'm sure you'll know just how unpopular IT can become if one was to just sack off department critical software You guys are all correct: WDS alone won't cut it, but sadly we don't have time to implement a new solution. MDT sounds great, but I'm away on my annual holiday from the 22nd leaving only two people to configure and deploy W10 to the rest of the 700 PCs. Prestaging PCs via WDSUtil etc is easy via powershell or batch files; it's the answer files that's having my life ha. Once Summer is done and the PCs are in and on a working W10 install, I'll look into upgrading to MDT. Ironically (and frustratingly) I told my colleagues right from the start that I wanted to (and I believe it's best practice) push out the images as thin as possible then deploy software later. What we've done instead is build the images quite thick and considered the most 'generic' department's image as the base. This will go out to many PCs of the same type and we're building custom images for other PC types and software suites. USing MDT/WDS as you recommend would get rid of all of this as we'd just be pushing W10 and injected drivers out to each PC type - no custom image required... One for the future, as we have Office 365 Exchange hybrid migration to tackle in September also...

We'll look into MDT in the future, but right now we need to get our existing solution sorted: installed windows 10LTSB Boot to audit remove all Apps and install software for that image type (maths software etc) do all tweaks and start menu icons (mainly for local account, as we're using folder redirection via a GPO) etc take a pre sysprep backup image Sysprep - currently we do /generalize /oobe /shutdown /unattend:unattend_W10.xml. Should I ditch the answer file here entirely, and rely on the WDSUnattend (to wipe and partition drives) and an Image assigned unattend.xml to do all the OOBE stuff? capture image using WDS. Deploy image to machines with WDS and prestaged devices using MAC addresses. As said, I was of the impression it's good practice to have WDSUnattend.xml applied to WDS server that has only the WinPE pass to wipe the drive and create the partition and set the InstallTo partition etc. We have the InstallImage blank so that theoretically, the only bit we're prompted for is the image to select. The Install Image should then have a more in depth unattend.xml assigned to have a fully automated unattend (OOBE etc all applied for us). So, using two unattends on the server, do I just sysprep the image before capture, but WITHOUT defining an answer file?

We're obviously still thinking in old fashioned ways. We're deploying W10 to ~700 PCs. How would you account for all the software that has to go on all of the PCs? Some of the software is really old too. We've built the image in audit mode and sysprepped it, then used WDS to capture the image. Is this the wrong way for W10?

We like to build the image, take a presysprep image with Ghost as a roll back in case of sysprep failure. This presents us with problems with BIOS settings. We have problems getting PXE and/or Ghost USB boot disks to read the SSD drive partitions. We've found it easiest to just do away with UEFI entirely, and rely on legacy boot. Perhaps it's not the modern 'proper' way to do it, but we've not encountered issues yet... will we? Does it really matter that we're running legacy boot mode on a modern OS/PC? Secondly, I'd like to ditch Ghost suite 2.5 entirely. Is it possible to use WDS to capture an image before sysprepping it? Thirdly, and sort of off topic; when building your main sysprep uanttend.xml, how do you make it fully automated? I want it so that the captured image prompts us for nothing when we boot it back up after deployment. Currently, it still asks us for locale, EULA, and all the stupid annoying sliders for privacy etc. SkipUserOOBE and SkipMachineOOBE are deprecated according to WSIM. Which settings do I need to skip all the slider settings etc? Thanks!

Hi Steve, Looks like my boss just cracked it. We'd tried everything, or so we thought. After registering it as 2012R2 for Win10, we tried registering it as 2016. Now, all of a sudden, all of the 30+ PCs are activating! https://www.linkedin.com/pulse/windows-10-enterprise-2016-ltsb-activation-issues-ahmed-ateeq EDIT: Ninja'd by Arthur. Yup, exactly as he said!

Woops, you're right. Removed the host key. yes, it has had a load of updates and the update for 2012R2 to activate win10. Do you happen to have the KB number so I can double check?

**Sorry, wrong forum!** My manager and I are being tormented by our KMS setup not dishing out license. We're running 2012R2 as KMS Host (same server as DC) with windows 10 LTSB 2016 clients. When building the image, we have entered the client setup key, which according to here, is DCPHK-NFMTC-H88MJ-PFHPY-QJ4BJ. This is in and accepted. The KMS server is online and set up and we have keys installed. The host is registered and activated withthe "2012R2 Server/DataCenter CSVLK for Win10" key. We have all the updates in that we have read about. When we try to activate a client, we get a message that the KMS server cannot be contacted. We can ping the IP, telnet via the 1688 port, and connection otherwise is fine. In VAMT, the devices show up when we discover them. Because they have the client setup key installed, they show up as GLVK with non genuine and status as 'notification'. If I try to activate the client from here, I just get the same error. Upon looking in event viewer ID 12288 on the client, it appears we get a license mismatch error. Great, perhaps we don't have the KMS client key installed? Is this the right way to think of it? There should be a host KMS key, client setup key, and client key. Correct? In which case, from where on the VLSC do we get the KMS keys that will activate Windows10 2016LTSB? We have three keys: two are 500 license MAK, and one for KMS. What is confusing me is that the product key title says Windows 10 LTSB 2016 KMS, with type KMS. Is this a client key, or when you use Windows 10 LTSB as the KMS host?! Any ideas? We've been going at this for days and short of creating a new 2016 KMS server we're stuck for ideas. Thanks!

Thanks, it's what I thought, but I don't have the technical knowledge depth about sysprep to put a good case across. I guess we'll find out one way or another over the next 6 weeks!

So, we've made our thin W10 image. We took a pre sysprep 'master' (more of a backup in case sysprep went t!ts up), then sysprepped it (with our W10_unattend.xml) and captured it with WDS. Now, we want to add more stuff to the image to capture a second one for a thicker image. I think it's best to push out the pre sysprep image, add photoshop etc, sysprep it again and capture the thick image to WDS. My colleague, however, thinks we can boot up the first sysprepped image, ctrl-shift-F3 it back into audit mode, then simply sysprep it again. What's the best method? Thanks,

Ah sorry. PP is Pupil Premium. It's not quite the kids in question technically, but it was the easiest way to explain them.

Well only two of the 10 students are under 13; the rest are 16+. I didn't know this when planning everything, otherwise the students leaving (not doing 6th form) in a few weeks would just have been given plain ipads with no restrictions and an iTunes voucher...

Thanks all. We're not talking loads of money here. £200 in total, so £20 per student. I'll not bore you with details but the devices weren't bought out of an official school budget and were aimed and PP kids. The devices are their to keep when they leave but whilst they're here, I'm locking them down for safeguarding purposes. It would just have been nice let the kids keep any apps that were bought during their education.

Yup, always have done. The past ones (before I started working here) were redeemable codes, but Apple kindly converted them all for me Here are my purchases with managed licenses I realise that I'm using free apps in that screenshot, but you have to have VPP licenses even for free stuff if you want to silently install apps. What I meant in my OP was this: if user A has an iPad that is device A (no iTunes account on the device) and I've assigned device licenses, how will user A's iTunes account (that they will create and use when they leave the school) be able to claim device licenses that were used when the device was within the MDM/school network?

I'm 99% sure the answer is no, but thought I'd ask, as I can't readily find a clear answer. Say I have 10 iPads supervised via AC2 and managed via Meraki and I have 10 app licenses purchases and assigned to devices, what happens when the device is wiped and no longer managed? Can that app 'transfer' over to the new 'open', non managed iPad, or is it stuck with the School for reassignment? We just bought £200 of VPP credit, but I've only just been told that the kids will be leaving soon and the iPads are essentially theirs. With them being under 16 I'd set them up on our MDM for the purpose of safeguarding (and the ability for us to remotely install apps for them) with the intention of wiping and returning them to the students as a personal device when they left. I figured that this would mean the £20 worth of apps would be wasted, but I (obviously, wrongly) figured it wouldn't be a problem as I thought it'd be 5 years before they left. Nope, turns out they're leaving very soon. Sooo, TL;DR: Can apps purchased through VPP and assigned to managed devices stay (transfer to) with said devices once they've been wiped and are no longer within the school network/MDM? Thanks!

I've not used that option, but I can vouch for a free MDM solution as a whole. It's always being updated and works well. 100 devices free, or that was the case when I signed up to it about 18 months ago.