headers
Bearly, Sean | 7 Nov 2005 18:10

RE: Auto Logon Issues

If these laptops are only accessing your OPAC why don't you have them only login to local computer? That's what we do with the laptops we checkout to customers - although we also give them full internet access and the MS Office products. All security is setup locally. The laptops automatically login as a local user so even if wi-fi connection hasn't been made by time they get to the desktop it is there shortly thereafter. To make setup easy I used the Gates public access computer profile tool and then we have McAfee and DeepFreeze. Our public wi-fi service is on the public side of our network so this is essentially how even our wired public access computers are setup.
 
Sean at Newport Beach Public Library
-----Original Message-----
From: Barry Moore [mailto:bamoore-0yC7V5IjiVG1Z/+hSey0Gg@public.gmane.org]
Sent: Monday, November 07, 2005 6:42 AM
To: LibWireless Discussion Group
Subject: [libwireless] Auto Logon Issues

We have dedicated OPAC machines that do nothing else.  Machines are running WinXP Pro and use an automatic logon for the user (through registry entries) that as soon as they start, they log on directly to the Windows domain, open Public Web Browser.  The machine is totally locked down with group policies to prevent access to anything else. The model has worked with machines hard wired to the network just fine for quite a few years.

 

We recently remodeled a branch library, and the branch manager wanted 3 new OPAC machines put in places where there was no wiring.  Not a problem since we have an internal staff wireless network, so we ordered the new machines with wireless NICs.

 

Our problem is that typically WinXP wireless connections (the NIC connection to the wireless access point) doesn’t connect fast enough, and the automatic logons process before the wireless is connected, therefore group policies are not implemented and security on the machine falls apart.  Is there a way to delay the automatic logon so that the machine connects to the wireless network first before processing the automatic logon?  Right now we’ve removed the auto logon from the registry and we’re logging the machines on manually and that is working.  Unfortunately, it’s a point of confusion for the staff since these machines are different from the others.

 

Thanks in advance for the help.

 

Barry Moore

bamoore-0yC7V5IjiVG1Z/+hSey0Gg@public.gmane.org

Library Technology Consultant

Vitrutech, Inc.

www.vitrutech.com

 

---
You are currently subscribed to libwireless as: SBearly-/VGGtjsubDhwu+c73Hs35QZaqqwxfqZv@public.gmane.org
The purpose of this group is to discuss libraries and all types of wireless technologies. This includes but is not limited to wireless LANs in libraries, accessing library resources via wireless devices, and
related issues such as WLANs, wireless bookmobiles, etc.

PLEASE LIMIT DISCUSSION TO LIBRARY AND INFORMATION CENTER TOPICS.
---
You are currently subscribed to libwireless as: gcgl-libwireless <at> m.gmane.org
The purpose of this group is to discuss libraries and all types of wireless technologies. This includes but is not limited to wireless LANs in libraries, accessing library resources via wireless devices, and
related issues such as WLANs, wireless bookmobiles, etc.

PLEASE LIMIT DISCUSSION TO LIBRARY AND INFORMATION CENTER TOPICS.
Permalink | Reply |
headers
Melissa Shepherd | 7 Nov 2005 18:43
Picon

RE: Auto Logon Issues

Your systems log on to a domain with the controller running 2003 server and Active Directory & you are wanting to retain the benefits of the domain including network printers that you can't access as a local user?
 
You can treat the logon on an XP machine as if it were Windows 2000(disabling fast logons) by applying Windows 2003 server policies to the organizational unit to which the user that is auto-logging on belongs, "User Configuration\Administrative Templates\System\Scripts\Run logon scripts synchronously" Your security is then fully processed before proceeding, and cached credentials are not used to "jump-start" the logon as they are in XP.
 
It may be worth a try, at least.
 
Melissa
 
Melissa Shepherd
Head of ITS
Huntsville-Madison County Public Library
Huntsville, Alabama
 

From: Bearly, Sean [mailto:SBearly-/VGGtjsubDhwu+c73Hs35QZaqqwxfqZv@public.gmane.org]
Sent: Monday, November 07, 2005 11:11 AM
To: LibWireless Discussion Group
Subject: [libwireless] RE: Auto Logon Issues

If these laptops are only accessing your OPAC why don't you have them only login to local computer? That's what we do with the laptops we checkout to customers - although we also give them full internet access and the MS Office products. All security is setup locally. The laptops automatically login as a local user so even if wi-fi connection hasn't been made by time they get to the desktop it is there shortly thereafter. To make setup easy I used the Gates public access computer profile tool and then we have McAfee and DeepFreeze. Our public wi-fi service is on the public side of our network so this is essentially how even our wired public access computers are setup.
 
Sean at Newport Beach Public Library
-----Original Message-----
From: Barry Moore [mailto:bamoore-0yC7V5IjiVG1Z/+hSey0Gg@public.gmane.org]
Sent: Monday, November 07, 2005 6:42 AM
To: LibWireless Discussion Group
Subject: [libwireless] Auto Logon Issues

We have dedicated OPAC machines that do nothing else.  Machines are running WinXP Pro and use an automatic logon for the user (through registry entries) that as soon as they start, they log on directly to the Windows domain, open Public Web Browser.  The machine is totally locked down with group policies to prevent access to anything else. The model has worked with machines hard wired to the network just fine for quite a few years.

 

We recently remodeled a branch library, and the branch manager wanted 3 new OPAC machines put in places where there was no wiring.  Not a problem since we have an internal staff wireless network, so we ordered the new machines with wireless NICs.

 

Our problem is that typically WinXP wireless connections (the NIC connection to the wireless access point) doesn’t connect fast enough, and the automatic logons process before the wireless is connected, therefore group policies are not implemented and security on the machine falls apart.  Is there a way to delay the automatic logon so that the machine connects to the wireless network first before processing the automatic logon?  Right now we’ve removed the auto logon from the registry and we’re logging the machines on manually and that is working.  Unfortunately, it’s a point of confusion for the staff since these machines are different from the others.

 

Thanks in advance for the help.

 

Barry Moore

bamoore-0yC7V5IjiVG1Z/+hSey0Gg@public.gmane.org

Library Technology Consultant

Vitrutech, Inc.

www.vitrutech.com

 

---
You are currently subscribed to libwireless as: SBearly-/VGGtjsubDhwu+c73Hs35QZaqqwxfqZv@public.gmane.org
The purpose of this group is to discuss libraries and all types of wireless technologies. This includes but is not limited to wireless LANs in libraries, accessing library resources via wireless devices, and
related issues such as WLANs, wireless bookmobiles, etc.

PLEASE LIMIT DISCUSSION TO LIBRARY AND INFORMATION CENTER TOPICS.
---
You are currently subscribed to libwireless as: mdshep-jjcc0KTbysFnL7yoowT4Mw@public.gmane.org
The purpose of this group is to discuss libraries and all types of wireless technologies. This includes but is not limited to wireless LANs in libraries, accessing library resources via wireless devices, and
related issues such as WLANs, wireless bookmobiles, etc.

PLEASE LIMIT DISCUSSION TO LIBRARY AND INFORMATION CENTER TOPICS.
---
You are currently subscribed to libwireless as: gcgl-libwireless <at> m.gmane.org
The purpose of this group is to discuss libraries and all types of wireless technologies. This includes but is not limited to wireless LANs in libraries, accessing library resources via wireless devices, and
related issues such as WLANs, wireless bookmobiles, etc.

PLEASE LIMIT DISCUSSION TO LIBRARY AND INFORMATION CENTER TOPICS.
Permalink | Reply |

Gmane