Garry1103

I get your point here, We've made it a point to be harsh about the whole "Lock your computer" situation, Then again I do agree with the statement the school has no reason to trust someones family members.

We've never had a problem with it. The only people who use our remote access use their staff laptops which have pretty strong passwords on them, then they have to use the VPN (A different password) then two more passwords before they can get anywhere. I know that sounds like the situation where people would write the passwords down but believe me I've never seen people with such good memories. The only thing we're concerned about with relation to SIMS is installing the application on devices that are taken out of the school, we outright refuse to do it.

We use our FortiGate for VPN handling, ontop of that we just use RDWeb just means people don't have a remote desktop open only the application they were after, which obviously is a lie because it has a RD session open in the background.

Hi @vikpaw Seems to have an issue with networked printers, we're using the PCounter system provided by Konica, for some reason FMS refuses to work with printers assigned to the computer. There are only 3 users who use FMS, total of 104 Staff though. Each computer is referenced by an OU of department for policy assignments as we have over 800 Desktops/Laptops/Tablets it's a pain to assign things to the local computer as if we ever replace it we'll of forgotten what we did to it. I don't object to having the extra 1 policy but I would prefer not to assign them to the users directly as they'll be able to print from one end of the building to the other, meaning some confidential information may end up where it isn't meant to be. EDIT: Forgot to say, Thank you for the welcome!

Hi All, I have read previous threads about issues with FMS and the runtime error 217 which is related to no default printer being selected. I've been tackling it for a week or so now and I seem to of found a solution however not my most favorite, I was wondering if anyone else has a better solution to the problem. When looking into what was happening with the FMS it only seemed to agree with manual assignment of the printer, this straight away becomes a problem in a domain environment with network printers. I attempted to use a command line to swap the printer to another and back again, this however still resulted in the runtime error. So Instead I played about with our Group Policy, I moved the printer from a computer policy to a user policy and assigned it to the people who use FMS with that printer. The issue is resolved from doing this however, this seems a little bit of a mess to me the less GPO's the better in my opinion. Is there any other way of solving this?