Sheridan

I use speedof.me - nice graphs and it seems pretty consistent

Anyone had any issues using the Translate app on IOS through a smoothwall? It works, but when you try to use the Conversation part it pops up with 'Google Translate was unable to establish a network connection to fulfil your request' which seems to just be a generic error. When the error appears I can't see anything being blocked on the Smoothwall, so is this another app that just won't work when a proxy of any kind is in the way?

Direct connection, no proxy, straight into the router!

This is a typical example of W10 - brand new surface pro I'm setting up for a personal user: a) The drivel of cortana wittering on annoys to being with b) Get through the setup and grind your teeth while the 'Hi...' stage completes c) Join to wifi d) updates fail e) Open Store - search for the app they want, find it, go to the Sign in part, only to be told I need to be connected to the internet, er....OK f) updates still fail g) printer installs - and remains greyed out and offline h) start menu hangs - the old favourite is back! i) store still insisting I'm not on the internet, despite two browsers working Ok and the store showing me all the apps! j) updates working, no only kidding, still failing At this point I've put the thing back in the box and gone home. I wouldn't touch a surface pro now, whatever the hardware is its hampered by this dog of an OS. Imagine how a complete non techy person would feel about this crap having spent over a grand on this thing!

Best description of W10 I've seen in ages!

How are you doing this in the script, by user or machine? We’ve tried doing this with the printui dialog for the machine policy but it just seems to ignore them

I thought I had, but I'm going to set it up and again and double check its being applied

Thats what I'd seen and tried but I couldn't get it to change the scaling - it just seemed to ignore it. I'll have another try!

Ahh yes but I'm trying to automate it a bit! - so it fixes directly onto a certain scale, plus it doesn't scale everything like text etc with the wheel.

Has anyone found a way to change the display scale (to say 125%) for certain users, on login with either a registry preference or a script? And possibly a logoff script to revert on logoff as well I've found a couple of reg keys to change but they don't seem to have any effect, and I only need to do this for a couple of users who move around a lot, so a GPP would have been ideal as I can set it for just those users.

After much testing and verbose logging all I could see was ours were hanging during the printer gpp deployment and the printers were online at the time. It was random and sometimes permanent, other times login would complete after a 10 minute or so delay which is just not acceptable. We don’t have user switching and it didn’t seem to be only related to first logins, as we have about 40 printers in the policy I was concerned about the impact it was having. After removing the gpp policy and deploying printers to the machine instead we haven’t had a single hang, logins are back to normal speed and printers appear 75-80% of the time, which is as good as it gets with windows 10!

I’ve had serious problems over the last couple of weeks, I was using GPP and item level targeting which was working about 80% of the time. But recently we’ve had random login issues across the network with logins hanging or taking 10 minutes, and I eventually found it always happened when processing the printers. So I’ve reverted back to deploying printers with machine based GPO, and this is about 75% successful, but no more hung logins. Makes me realise MS are just not fixing anything and just continue to fart about adding features no one wants to their ‘updates’

Hmm that's a good idea, they wanted to sell the DVDs originally but that's only to cover the cost, it wouldn't stop anyone sharing the link but this is always going to be a problem whatever the media they use

Yeah - I can buy something to add copy protection, but that would mean burning them one by one as it would stop our duplicator Plus any savvy user can rip them using DVD Shrink or similar anyway!

Interesting question from one of our schools, they'd like to create a copy protected DVD (their own videos) to give to parents. I'd assume this meant buying special DVD burning software but I'd be interested to hear any recommendations as theres a lot of them around! They'd also want to them copy the DVD (the irony!) in reasonable bulk, so I'm not sure if these two things are at odds with each other. I can see why they don't want the videos ripped and chucked on social media, but ultimately can you ever stop this!

This is turning into a nightmare, its happening in random places, PCs just hang at Welcome, and the last thing logged was "The winlogon notification subscriber is taking long time to handle the notification event (Logon)." But you can browse the C: drive remotely, connect to the event viewer etc, but you can't login and once its stuck in this state you can only recover with a cold boot. I'm really looking forward this when everyone is back next week! The detailed gpsvc.log shows its hanging during the printer preferences stage - but no real clue as to why, it just stop dead and no more logging happens either. GPSVC(198.23c) 10:39:23:483 ProcessGPOList:++ Entering for extension Group Policy Printers GPSVC(198.23c) 10:39:23:483 UserPolicyCallback: Setting status UI to Applying Group Policy Printers policy GPSVC(198.23c) 10:39:23:489 LogExtSessionStatus: Successfully logged Extension Session data GPSVC(198.23c) 10:39:23:490 ProcessGPOList: lpGPOInfo->lpGPInfoHandle->dwExtnCount is 2 for Group Policy Printers. GPSVC(c14.c34) 10:39:23:740 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000005BC GPSVC(c14.c34) 10:39:23:740 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c34) 10:39:23:761 CGPNotify::RegisterForNotification: Entering with target Machine and event 000000000000060C GPSVC(c14.c34) 10:39:23:761 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.15bc) 10:39:23:784 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000007AC GPSVC(c14.15bc) 10:39:23:785 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(240.1c4) 10:39:25:512 CGPNotify::RegisterForNotification: Entering with target Machine and event 000000000000022C GPSVC(240.1c4) 10:39:25:512 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(240.1c4) 10:39:25:513 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000284 GPSVC(240.1c4) 10:39:25:513 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c30) 10:39:28:682 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000CD8 GPSVC(c14.c30) 10:39:28:682 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(c14.c30) 10:39:28:683 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000D20 GPSVC(c14.c30) 10:39:28:684 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(580.4cc) 10:39:33:782 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000214 GPSVC(580.4cc) 10:39:33:782 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(580.4cc) 10:39:33:783 CGPNotify::RegisterForNotification: Entering with target User and event 000000000000026C GPSVC(580.4cc) 10:39:33:783 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(e78.df4) 10:40:21:609 CGPNotify::RegisterForNotification: Entering with target Machine and event 0000000000000438 GPSVC(e78.df4) 10:40:21:609 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(e78.df4) 10:40:23:622 CGPNotify::UnregisterNotification: Entering with event 0000000000000438 GPSVC(e78.df4) 10:40:23:622 CGPNotify::UnregisterNotification: Exiting with dwStatus = 0x0 GPSVC(eb4.c84) 10:40:25:081 EnterCriticalPolicySectionEx: Machine from process 3764. GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Entering with usersid = (null), timeout 600000 and flags 0x30000000 GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Making Aync RPC LockPolicySection call GPSVC(eb4.c84) 10:40:25:081 Client_LockPolicySection: Beginning WaitForSingleObject. GPSVC(198.548) 10:40:25:082 bMachine = 1 GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Completed WaitForSingleObject. GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Machine critical section has been claimed. Handle = 0x00000235FC6865C0 GPSVC(eb4.c84) 10:40:25:083 Client_LockPolicySection: Leaving successfully. GPSVC(eb4.c84) 10:40:25:273 Client_UnLockPolicySection: Starting UnLock Call GPSVC(198.548) 10:40:25:274 Setting lock state as notLocked GPSVC(198.548) 10:40:25:274 CPolicyCriticalSectionCollection: Deleting critical section for UserSid <(null)> GPSVC(198.548) 10:40:25:274 Deleting machine GPSVC(eb4.c84) 10:40:25:274 Client_UnLockPolicySection: Unlocked successfully GPSVC(eb4.c84) 10:40:25:275 LeaveCriticalPolicySectionInternal: Critical section 00000235FC6865C0 has been released. GPSVC(398.1224) 10:40:33:196 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002EC GPSVC(398.1224) 10:40:33:196 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(398.1224) 10:40:33:197 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000338 GPSVC(398.1224) 10:40:33:198 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(15d8.c68) 10:40:33:436 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002CC GPSVC(15d8.c68) 10:40:33:437 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(15d8.c68) 10:40:33:438 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000318 GPSVC(15d8.c68) 10:40:33:438 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(ce4.bfc) 10:40:33:486 CGPNotify::RegisterForNotification: Entering with target Machine and event 00000000000002CC GPSVC(ce4.bfc) 10:40:33:486 CGPNotify::RegisterForNotification: Exiting with status = 0 GPSVC(ce4.bfc) 10:40:33:488 CGPNotify::RegisterForNotification: Entering with target User and event 0000000000000318 GPSVC(ce4.bfc) 10:40:33:488 CGPNotify::RegisterForNotification: Exiting with status = 0

I got around this by simply running two scripts, one at login and one at log off which copies their local Bookmarks file to and from their network home share, it’s worked pretty well for a couple of years and has the benefit of their bookmarks being included in our backups! They’re pretty small files so I haven’t had any issues with the copy process causing any delays

That’s the thing, the multiple copies of the same printer are all showing exactly the same driver, down to the version number!

And it gets weirder - still happening randomly even though I thought I'd found a reason, and I've now noticed that some of the PCs show mutiple (i.e 5+) copies of the shared printers! So if they have 3 printers assigned to them in GPP they can see 15-20 of them in the Printers control panel - but only the 3 show up in an application such as Word.

We do use Sophos but only for AV, not the malicious software stuff? We're still having logins freeze occasionally on other PCs as well, so my 'fix' isn't working everywhere. I guess staff here have got used to rebooting their PCs when a login hangs so often they just don't tell me anymore! It looks like I'll have to revert back to the old scripted printer installs, printers don't work with GPPs in W10 anymore it seems

Well it looks like this one is down to printers - which is a depressingly familiar problem with W10. It seems that because these PCs have 2 shared printers deployed to them (using User GPP deployed printers and item targetting) it causes the problem - and the only reason I can see is that the two shared printers are the same model/driver, which seems to cause the logins to 'lock' when the drivers are being installed, perhaps stuck in a race state? Changing the driver on one of the printers to a Universal driver and we haven't had a failed login since. Verbose logging hangs on the Group Policy Printers stage. The Register is right, W10 is a sh-t shower - this problem would actually cause the PC to hang at the Welcome stage (and it would never recover, we even left one for 24 hours) and a cold boot is the only solution. It was random, but presumably that was just down to the printer driver installer overlapping itself sometimes, other times they maybe completed synchronously and therefore worked. We still have the same problem of the printers not appearing until the second login, but that won't ever be resolved unless we go back to Windows 7!

Nothing in the standard event logs, just the normal group policy processing messages, the same set of events appear for a normal login as for a failed one. I’ll try and get some verbose logging and see if it reveals anything.

We’ve got a bunch of around 20 pcs, of differing hardware but all the same 1703 w10 images that are really frustrating me with a login problem. Randomly, a users login will just hang at the Welcome stage, and stay there indefinitely. Rebooting may work, and it affects all users including admins, although it seems less so with admins. We’ve tried updating some of them to 1803, but it made no difference and the event logs show nothing significant, just the normal messages you’d see during a login, but it just stops at that stage. This is on 4 different types of hardware, and this is where is gets a bit weird, if we move one of the pcs to another room and another switch it seems to work, but moving any pc into its place also works fine as well! Our switch configs are identical anyway as the switches are all the same so I’m doubting a network issue, and we do have other pcs on the same switch that work fine, but using a different image, and even pcs on the same subnet but a different switch work fine as well. So it’s the combo of this image on this switch cabinet that I can’t fathom, anyone seen anything like this before? Ironically when the pcs were all running w7 previously they were absolutely fine!

I’m going to run another reindex and see if that’s helps. That’s pretty much all capital suggest these days.

Yes, our complaints have been mainly in the last 3-5 months, and seem to be more regular now than ever before!