DanArkless

We do at our other site but its in no way connected to these PC's. We're using a SonicWall. It's definitely something to look into and we do have something similar set up. Thank you!

It's not every time and we can't find a pattern, its happened to other members of our team but it happened to me for the first time the other day. Hasn't done it since but my colleagues in the office get it quite often, maybe once a week. Seems to be multiple users with different permissions.

1. We've done scans and nothing found, possibly could be a GPO 2. Yes, but very random and not all the time. At the moment not all PC's have had this reported back to us 3. Any user profile, new or existing 4. Server 2012 R2 5. Will try that! However it's so random, sometimes it happens once a day sometimes only once a week 6. Yes, has been since we pushed out 2016 and is up-to-date 7. Yes It's such a strange one I'll admit! Thanks

Sorry, that was a poor description. As in locks the computer as if you were to press Windows+L. We then have to log back in after this happens.

Hi there, We're currently using Win10 1709 and for some unknown reason on occasions when we close Word (2016) it locks our desktops. Has anyone else experienced this? Thanks

Hi, I've been using MDT to deploy Windows 7 and Windows 10 for a while now and Windows 7 has never been quite right. For some reason it's installing the OS with a 52GB DriverStore folder. Within my MDT the OOB Drivers only totals 4.4GB. Does anyone have any experience in anything similar? Edit: The image was captured from a clean install with only the network driver and Windows updates. Many thanks

It depends what settings you're changing, are they computer settings or personalised settings? Most settings which you may be changing may only be changeable via Group Policy afterwards with various different ways to do so. --- I'm capturing my Win10 images on a physical machine with WDS and deploying through MDT so if there's any difference between the two I cannot give my opinion ---

I've made a new profile with only a handful of drivers in, then I've only chosen that profile with "Install only matching drivers from the selected profile". It still seems to be installing all profiles as originally my driverstore folder was 60Gb+ and I've got to down to 30Gb with only 1 profile as before it was set to install all profiles for drivers and packages. The drivers that are in the specific folder were only driver for 1 PC totalling at probably no more than 400mb. I can't for the life of me find out why its still insisting on pulling more than what I've specified. Edit: Can I delete old profiles which I know we no longer use (old PC's) which members of the IT team set up a long time ago? To try and solve the issue.

I had a similar issue, after completing our Windows 10 deployment it would sit on the local admin desktop and fail to continue to install anything more than the OS itself. I rebuilt an entire new image, straight from an ISO from Volume Licensing site, installed all updates etc, and then created a unattend.xml by following the first section of this GUIDE under the ADK bit. After this, my unattend file works perfectly and the task sequence handles the rest within MDT. My applications now install, the only thing I have different compared to my Windows 7 deployments is that I don't attach any profile to install drivers or packages under the task sequence. Hope you've sorted it by now, let me know if you need anything more explaining.

Hi all, I've looked all over Edugeek and on MS tech forums but I'm unable to find out a solution. So I'll try and explain my issue here. I've set up MDT 2013 and have been deploying Windows 7 and newly Windows 10 perfectly fine. That was until I noticed that my DriverStore folder on 'C' drive on all of my Windows 7 deployments were 30GB+. The steps I took to set up my Windows 7 deployment are as follows, and by doing this I thought MDT would only be injecting drivers which it needed. - Imported all relevant drivers into MDT through Out of Box Drivers - Captured my image after using sysprep and attaching an unattend file and imported it into MDT under OS - Create a Task sequence using my Windows 7 wim - (Task Sequence) Created a Profile to use within Out-of-Box drivers (Windows 7 x64) for example, and selected it - (Task Sequence) Selected my newly created Profile within Apply Patches - Updated Deployment Share - Completely regenerate the boot image I have also created an up to date Boot image within the Deployment Service. Please outline any faults that may be causing this or if I have missed a step, I'm sure I've included everything. Any help is greatly appreciated. Thanks

We don't use a VLAN for our Guest Network, I'm not sure if this is possible on other networks that you set up with security.

Hi there TomHD, We currently have a guest network set up on our Unifi controller. We use a separate VLAN and we have it set up as a Hotspot and have the Voucher enabled as authorisation. In the means of restricting the guest users from browsing our internal system we use the Access Control which is found under the guest control, we have then just added restricted subnets.