Jump to content

matthewfarnell

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by matthewfarnell

  1. hi, we have started having an issue recently with group policy not applying things here and there. We recently re implemented group policy printer deployments as our old method was getting a bit sluggish. So cut a long story short we built the gpo's, linked them to the container, right clicked and did an update on the ou and got a box which counted through the pc's. they all gave an error code 800706ba. the RPC server is unavailable. We did a bit of googling and saw it is a firewall issue. So, we disabled the firewall on the pc's (and checked them). Still same error. We've also tried removing our antivirus (Sophos) from some of the pc's to test it and no luck. Any one had this before
  2. hi, we have just moved to windows 10 and experiencing the same issue across the site. We have sb500 and 600 series. We have already had the driver issues with the sb500's and managed to fix that by using the new drivers so all our boards are connect. our issue is when powerpoint is in presentation mode. Users are reporting that they can be halfway through writing on their powerpoint and it will just go back into pointer mode, thereby stopping the pens. Has anyone else had this issue? Thanks
  3. We use FSM to control user quoters and also we have dedupe turned on on that disk. (Don't know if the benefit of of dedupe actually shows as available space to them in their docs tho).
  4. hi this is just a quick publish on a problem we came up against and solved, incase anyone has the same issue. From windows 7 Microsoft have some bizar method of naming for users documents when storing on a file server. It creates a file called desktop.ini in the users documents and from the moment this is done, their folder will only show as "Documents". Not by the name you define in AD. To combat this we discussed with some other local schools and they had set a script to delete all desktop.ini files on the file server, and schedule it so any new users it will catch and correct. Jump forward 5 years to Windows 10. We are now looking at changing our profile system. We realised that after a period of time the users login became slow. Not directly after it had been created but shortly after. We tested taking the users directory to another server, this worked. we took the directory to the c drive of the file server and that worked. We rebuilt the server and re added the user documents drive and that worked fine. We thought we'd fixed it. We thought it may be a formatting issue or an access issue. Then all of a sudden it started again. So we back tracked everything we had done to the new server to get it up and running. Volume shadow copy, permissions, and desktop.ini removal script. So we added a new drive, and applied each of the above in turn, until we found out it was the desktop.ini removal script. A users profile will struggle to build if it fails to see the desktop.ini file. Thus causing a 2 minuet addition to our logon times. I post this because so many of our local schools copied each others method for windows 7 profiling and may encounter this issue. Simple fix allow the desktop.ini file and if you need to find a users folder, change your field names at the top of explorer to show "filename". This shows the true folder name.
×
×
  • Create New...