Sheridan

We've run WSUS on our network for as long as I can remember, most recently on a 2008 R2 server. I noticed most of the Windows 7 client stopped reporting in a good few weeks ago. Nothing I tried on any of these machines (reseting the id, running the full wsus script to reset the components etc) seemed to make them connect to WSUS anymore - they simply showed up on the server as 'Not yet reported' So I removed and reinstalled WSUS on the 2008 server - same result. I then built a VM, installed Server 2012 R2 and installed WSUS on that, redirected the clients to the new server and same result again! And now WSUS on the new server cannot be accessed as it constantly comes up with the Reset Server Node error, even after deleting the file from the user profile that MS suggest as a fix. So apart from the fact I can't get WSUS to even run properly on 2012, does anyone know if there was a Windows 7 update since maybe July/August that broke WSUS? We had ours setup to automatically authorise Critial/Security updates which I guess is what most of you do? Other than that I can't see any way forward unless I a) ditch WSUS or b) start reimaging 100's of W7 PCs!

Yes thats still visible - and WSUS is working for maybe a third of my PCs, the others seemed to just stop around the time I converted it!

In my case it looks like my WSUS setup is now borked. Before the holidays it worked fine, with all W7 clients connecting. I converted that server to a VM in the middle of the holidays and now at least half of the W7 clients fail to connect and all log the error "Windows Update Client failed to detect with error 0x80072ee2" So I guess I've got bigger problems than the handful of W10 machines that won't connect!

We have the UPN set to our original domain name, the GAFE is our new domain name - just to complicate things! I guess if I can sort out a script I could set the users mail attribute to the userlogin@newdomainname format and then GADS would work as normal. Actually, I wonder if you can enter a custom entry in the Email Address Attribute in GADS? something like sAMAccountName & "@newdomain.com"

Has anyone got a recent guide on how they set this up? One thing I've noticed is that GADS seems to use the AD mail attribute which we don't have set at the moment. Basically I want a very simple synch of all user login's and all groups from two OU's!

We are running Wsus on server 2008 r2. It seems to not work for any Windows 10 machines, and now only perhaps half of the Windows 7 machines. The last date date seems to coincide with when I converted the physical Wsus server to a virtual one. However that doesn't explain why in a room of Windows 7 pcs half are connecting and half aren't! Our Wsus server seems to be detecting windows10 as the OS but the clients fail to connect, so they must have connected at some point to register the OS!

None of the 10's I've tried it on have reported into WSUS. Oddly a lot of my W7 machines have also stopped reporting, but a large amount are still working! - so my WSUS server might be completed shafted.

I've applied the latest update today and WSUS is still broken, none of my W10 clients are reporting to WSUS anymore.

It did have the same filename, so I tried with a new filename and it makes no difference - it simply hangs on to the first lock screen that was deployed by GPO. Can't be faffed manually changing permissions on all of them, its anothe reason I feel justified in the impending roll back to 7!

Perfect, that's what I was hoping someone would say!

Another bug for the list. We pushed out a default lock screen which seemed to work ok, however a week or so later we needed to change this screen and rolled out the new image. However, only half of the PCs show the new lock screen, the other half show the old lock screen. But, on every machine the \windows\web\screen folder shows the correct new lock screen - I know this is cached somewhere and has to be manually deleted after permissions are reset but thats a massive pain in a room full of computers. I guess I'm waiting for another update, unless theres a way to force the cache to clear?

We resolved it by.....default browser is now chrome!

We currently have GAFE with a VLE plonked on top - the VLE uses its own synch tools to pull data from our MIS to create/synch users etc. However we wish to change this, to seperate the VLE and use GADS to pull data straight from our AD servers - all good in theory but I'm wondering if it will cope with the existing users in GAFE, as the usernames (i.e AD logins) are the same. So anyone whose account was created using the prior VLE synch should keep their same account, but the password would synch with their AD account rather than the vle generated one. With me not being very familiar with GADS, does that sound feasible to anyone who has done anything like this?

Our upgrade from xp to 7 was a breeze compared to this. We tweaked an image of 7 and rolled it out. Apart from a few tweaks and program specific issues we carried on for years. Two weeks with this cludgy mess that 10 is and were ready to roll back. Our job is to provide a reliable tool for the staff and students to use, 10 is not allowing this at the moment and is more of a hindrance.

Its made me realise how solid Windows 7 has been over the last few years. Even Applocker can't be relied on as well as the old SRP.

Since we updated our image to 1607 we've had more issues than ever. IE11 has to be re-enabled, which then means all users are asked for their default app choice again - which means they then have to have permissions to change default apps! Its so unreliable as well - 'Group Policy service failed the login' is now a regular error I hadn't seen since we tried out Windows 8.

Anyone else decided to do this? We did lots of testing with 10 but in our small IT Suite where we deployed 10 we've had enough complaints and issues to warrant rolling back to 7. Basic stuff like the Start menu hanging, 'Please wait' permanently on boot, failing to connect to WSUS, failing to connect to printers, failing to login,hanging on 'Locking' etc are showing that 1607 breaks as much as it fixes. So for now, we ditch 10 and welcome back 7. Maybe in a year or two Windows 11 will sort these out.

Yup, latest flash installed here and not working on ie11 so basically given up and used chrome.

It worked in compatiblity mode until very recently. I could never get it to work in html5/normal mode - just the endless spinning circles. I've tried on Win7 & Win10 and it fails for anyone (admin,staff,students) so unlikely to be a policy issue. I've also tried as an admin bypassing the smoothwall filter and it fails as well. So it fails pretty comprehensively across several OS's and versions - thats where I'm stumped and ready to finally give up on it!

Well, it seems that IE11 will no longer work with youtube no matter what I try. In compatibility mode it says it needs flash installing (even though flash 22 is installed and verified) In normal mode you just get the endless spinning circle and no video In Chrome it works fine. For us that is the death of IE, no youtube, no use!

Don't think there's a specific requirement but we bung the leavers work onto a cheap NAS box and delete the oldest as it fills up, we probably have 3-4 years of leavers including staff.

I'll just live with it, past experience shows taking your phone back means you're without it for weeks and all they do is a factor reset before giving it back!

Ahh looks like mine is dodgy then. Either that or I have an apple only finger. An iFinger perhaps.

To be honest I've tried dead straight and moving my finger all over at different angles. Makes no difference. I know my finger isn't at fault as it works fine on my iPad! [emoji3]

Anyone else out there with an s6 edge use the fingerprint scanner? I've tried so many times to get it working I can only assume the scanner is knackered. I can register a print, but unlocking it it nearly impossible, it might work once in 20 attempts so I can't use it as the phone ends up locked! It's running the latest update as of today so I'm wondering if the scanner itself it's at fault as I've only had the phone a few months.