|
|
Requesting feedback for Gates Security Tool or granted PCs
1:21 PM EST 1/5/06
Hi-
Chris Peters, from WA State Library and I are going to write some library specific instructions for using the new MS Shared Computer Toolkit to lock down PACs. As part of that, we are interested hearing what you do and don't like about either your granted Gates Library Computers or the Gates Security Tool you have installed on other computers.
Any answers to the following questions would be greatly appreciated. Or any other suggestions you have.
What features are the best/most important to you? What features cause you the most trouble? What would you change about the way the security is set up? What features do you wish it had that it doesn't?
Thanks for your help in this - it should help us make something that is more useful to more librarians.
|
|
|
|
|
|
Re: Requesting feedback for Gates Security Tool or granted PCs
10:37 PM EDT 9/21/06
as a reply to Patti Lehman.
Patti- <br><br> Chris and I did get around to writing up some library related instructions for the toolkit. The basic set is <a href="/do/DisplayContent?id=13386">here</a>. <br><br> In those instructions, particularly look about 2/3 of the down for the "Prevent access to some Windows Explorer features " setting. I think that is the one you need to turn off to allow access to the system tray for Cybersitter. There is also a printable version of the instructions linked at the bottom. <br><br> And there are a few other related articles that you can find in the <a href="/do/Navigation?category=528">Security Category</a>. <br><br> Dale
|
|
|
|
|
|
Re: Requesting feedback for Gates Security Tool or granted PCs
2:15 PM EST 11/10/06
as a reply to Dale Musselman.
I finally got a day to work on the public access computers and I have run into a problem 10 minutes in. I am following the instructions in the document "Locking and Unlocking Profiles with the Shared Computer Toolkit" Under "Creating Custom XML Files" I followed the directions to step number 7. After I double clicked CreateRestrictedSettings.bat I received an error message in a window titled "Shared Computer Toolkit: Windows Script Mode Detected". The error message was Restarting script in command-line mode. Run CmdOn.bat to set command-line mode as the default mode. I double clicked on the CmdOn batch file in the same directory. It did its thing, but the CreateRestictedSetting.bat is still not creating an XML. What do I do now?
Is it possible that the syntax is not correct in the instructions?
Also it would be a good idea to put in all your documents a Last Updated date, so that users know how old the documents is that they have printed out.
|
|
|
|
|
|
Re: Requesting feedback for Gates Security Tool or granted PCs
12:13 PM EST 11/22/06
as a reply to Patti Lehman.
Patti,
Hope I haven't kept you waiting too long, but I took last week off.
I got the same error message that you got, which I don't recall seeing when I wrote the instructions. However, the XML file was still created, and it worked as it was supposed to. So we might be dealing with two separate issues. It sounds like the error message went away when you double-clicked CmdOn.bat. And that worked for me as well.
The other issue is the abscence of the XML file. A few suggestions:
1. My batch file looks like this: "Restrict.wsf /User:lab /Create /XML:labRestricted Pause" The word "lab" should be replaced with the name of your public profile. Make sure you've already created this profile and locked it down with the User Restrictions tool. Then make sure that the spelling and case in your batch file exactly match the real name of the profile.
2. When you double-click on CreateRestricted.xml, were you in the C:\Program Files\Shared Computer Toolkit\scripts folder? And do you see a file called restrict.wsf in that folder? The batch file is calling restrict.wsf, so it has to be in the same folder as the batch file.
3. The XML file should appear in the scripts folder as well. It may show up at the bottom of the list of files, out of alphabetical order.
Also, bear in mind that these batch files aren't essential to the working of the Shared Computer Toolkit. They're mainly useful if you'll be making lots of changes to your profiles. Also, they're useful if you've enabled an unusual, complicated array of security settings within the User Restrictions tool. If you won't be making any changes to your public profile once you've locked it down, there's probably no point in creating these batch files.
|
|
|
|