Jump to content

dhoward_westexetc

Members
  • Posts

    243
  • Joined

  • Last visited

Reputation

125 Excellent

About dhoward_westexetc

Personal Information

  • Occupation
    ICT Technician
  • Location
    Exeter, Devon
  1. I had this myself. If you look at my post 33 on this thread http://www.edugeek.net/forums/educational-software/124240-pearson-onscreen-platform-installation-woes-3.html#post1091267 you'll see my solution, which basically involves configuring one machine per room, then taking the config files and storing them centrally. Deploy to the relevant system using group policy preferences and loopback, but only applying to the exam accounts. GPOs assigned to the computer OU, hence the need for loopback. Worked for us for 3 years.
  2. I think in our case it was a bug in Windows 7, and I don't think it got fixed until the Enterprise hotfix rollup. But as I had spent so much time perfecting our scripts, and the fact they work so well, i'm reluctant to rip it all up and go back to group policy again.
  3. Domain share - but Netlogon works equally well.
  4. Good idea. Looking at it, seems easy too. Thanks!
  5. Used GPO and GPP for a while. It was an utter disaster, as printers would randomly fail to deploy. So I went back to VBScripts and they've been rock solid ever since. Now working on V2 scripts that would take the left side of the computer name (the room number) and use a Select Case statement to assign the correct queues. I also have a thin client version too I am developing.
  6. We will be this summer. We've found too many sites in general do not work properly now on IE, but do in Chrome.
  7. Just realised that there's a link there for the new kits, including the new ADK! I'm going to download and give it a go with build 14366!
  8. Does anyone know if the Windows ADK (which includes the ICD) for the anniversary update is available at all? I know it's needed to enable shared PC mode for local AD-joined Win 10 1607 systems, was hoping to test this that's all.
  9. Just picked this up, as I have run into the same issue myself. Where was the different installer you found, I tried searching in AppData\Local\Temp, but could only find the 400MB+ MSI file.
  10. You can exclude Roaming App Data from the User profile disk too, but I've left ours as default, which puts chrome data on AppData\Local\Google.
  11. I implemented comment 43, which says about not redirecting local folders, but added the folder AppData\Local\Google to the profile. Seems to fix it in my single server environment, but cannot say if it works reliably in a farm deployment as I don't have a farm. It will work for now until hopefully there's some traction on this with Google.
  12. Nice one, thanks. Couldn't find that on my search! Good to know it's with them. Agree, it's a highly needed fix.
  13. Thanks @KibosJ. Thought it may have been to do with that. Very interesting, especially as User profile disks have been around for a long time. I haven't been able to see anything myself that indicates that Google are aware of the issue.
  14. Currently working on deploying Chrome via the MSI, and using group policy to deploy settings. Among our settings is that we use the Chrome > Extensions > Force Install extensions to install the Impero extension for web filtering. It works perfectly on Windows 7/10 client, but if I do it on our Server 2012 R2 RDS server, it doesn't install the extension. All other policies work fine. Server is configured with User Profile Disks Anyone else had this and know a way to make it work? Thanks!
  15. For us it is a compromise between having a heavily customised profile while still keeping login times as short as possible. But we still have logon times at ~63 seconds for rotating disk and, when I tested one SSD fitted system, ~39 seconds. I am hoping to be able to fit more systems with SSDs. Along with the profile copy, the next stage that is slowest for us is the Folder Redirection Policy, which takes a few seconds to apply. We redirect most things - Documents, Desktop, Start Menu and so on. Not sure what impacts that so much, suspect maybe our switchgear (which is long overdue for replacement anyway) is having the main effect.
×
×
  • Create New...