spd_demon

Hey all, I'm in Canada, have over 75,000 chromebooks deployed and we have been struggling with this as well. We used the "erase local data" in the past and has been hit or miss. We too were told we needed a trigger for logouts so we implemented the Idle setting to be log out. This proved problematic as others have stated. What I'd like to see from Google is a policy option that would be supported on the chromebooks that would erase cached copies of profiles that haven't been used in X amount of days. This would allow us to maintain user data on devices but would never run out of space.

Hi all, Just a question to you all as to how you are managing your applications and the deployment/management of them? We have 80,000 machines, almost 400 apps, 210 locations, SCCM CB deploying Win 10 Ent. We have looked at so many delivery options, SCCM, VDI, App-V, Citrix, TS etc. etc. No one technology seems to fit the need without spending an arm and a leg. Curious to how you folks are deploying your applications to Windows devices? Thanks for taking the time. Kevin

Another option that I have used is to enable "IPP" or Internet Printing Protocol on your print server (if it is a Windows box). This enables users to open a webpage that lists all printers on the server and gives them the ability to install them by choice. What I do is install the service and publish a desktop shortcut or internet favorite that points to http://servername/printers (default location). This only works in IE but it is super easy. If you have multiple print servers, you can target servers to users by using environment variables (%printserver% = servername) so that each users shortcut is tailored to the location they are at. The link would then look like http://%printserver%/printers.

It's actually the same thing. If you go to the "Labs" installers (in Dreamspark), it gives you the same version. If you login to it, it changes from trial to activated. But only for 90 days. Additional logins are required to keep it "activated". Says trial but it is misleading. We too are now using Visual Studio Pro 2012 as that is the last version to support a product key.

How are you guys getting around the trial / ms login issue? The suite will need to be reactivated every 90 days and we just can support that in our environment.