mproffitt1983

Double-tap

Yes, we're in the same boat. Been very slow all morning and now nothing.

We point ours to the 'o' attribute in AD which is populated with our domain\username GCDS - Custom Schema Schema Name = Enhanced_desktop_security Field Names / Google field = [AD_accounts] LDAP field = o Hope this helps. Matt

We use salamander to populate the 'o' attribute in AD then use GADS custom schema to populate the AD attribute on the Google side. If you are having trouble with new user profiles it may be worth trying FQDN\username for your attribute rather than DOMAIN\username of not already.

If I'm updating a previous install I use the following command \\networkpath\AcroRdrDCUpd####.msp /qn

We use Chrome Remote Desktop quite a bit. You might need to unblock some URLs for it to work onsite. remotedesktop.google.com remotedesktop-pa.googleapis.com play.google.com

Shame I only found this discussion now! [emoji30]

?

I just ran into the 'Windows Search Blank' issue. The same workaround may also work for your situation. I just added the following DWORD into registry and logged off and on again. It does disable Bing search though. [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search] "BingSearchEnabled"=dword:00000000 https://www.bleepingcomputer.com/news/microsoft/windows-10-search-is-broken-and-shows-blank-results-how-to-fix/

We backup the C:\users folder before we wipe admin machines. We do inform staff that data saved to the desktop isn't backed up but we still get a few files now and then - we would then dump the files in their home directory or wait until they realize they're missing something. We use the following script. net use w: \\networksharepath w: md %computername% robocopy c:\users\ w:\%computername%\ /MIR /XA:SH /XD AppData /XJD net use w: /delete pause

Thankfully we are only configuring chromebooks for a primary school on our site, we don't actually use them ourselves - this would have been a big issue otherwise. We have the following URLs unblocked to allow Croudready activation, Google sign-in and also QR sign-in. Hopefully these are helpful to others here: android.clients.google.com mtalk.google.com gvt2.com gvt3.com hangouts.google.com accounts.google.co.uk accounts.google.com bootstrapcdn.com clever.com neverware.com assets.clever.com samlidp.clever.com maxcdn.bootstrapcdn.com alt2-mtalk.google.com alt5-mtalk.google.com alt8-mtalk.google.com android.clients.google.com beacons.gvt2.com beacons3.gvt2.com beacons4.gvt2.com beacons5.gvt2.com beacons5.gvt3.com crl.pki.goog/GTSGIAG3.crl mtalk.google.com - - - Updated - - -

We also have the same Chromebook issue. It will work sometimes and not others. Called today and they have added some sub domain urls that appears to have helped. Why you need to add sub domains when root domain is allowed is beyond me. Maybe something to do with hidden lists. We are now at a point where Chromebook signin works more often than not but it can be extremely slow. Feels like there are many policy lists involved here and they're all fighting to decide whether to allow or deny a request. I think more information about the actual setup of NetSweeper should have been provided to schools.

The console doesn't seem to like me navigating too much between policies and log viewer. Gets to the point where it is unresponsive. I'm forever unblocking services because SSL inspection is breaking ChromeOS signin and Cloudready activation. The Policy seems to apply one minute and not the next. I also find that global allows don't work that well - we have to add urls to each user group.

Our printers install with Group Policy if we give them enough time (about 5 minutes before login) Maybe try enabling this GPO from http://www.edugeek.net/forums/windows-10/191185-disappearing-printers-16.html Computer Configuration > Administrative Templates > System > Device Installation > "Prevent device metadata retrieval from the Internet" - Enable The Policy might be hanging while the metadata is collected (or not) from the web.

We have run into issues with this before. We ended up using WoL to power up the workstations about 5 minutes before they're used. This seems to give enough time for the printer policy to apply - it's not ideal but works for us.