Active Directory Login After Sleep?
We finally have a group of about 35 users with Mac OS X 10.4.1/10.4.2 (we're getting everyone up to date slowly) who are logging in against our Active Directory at work. Our network includes about 200 Macs and 10,000 Windows PCs. We've configured the Directory Assistance utility and bound the workstations to the AD and almost by accident discovered we could then login this way without manually creating users first. They have a variety of different hardware configurations: Dual 2.7GHz G5s, Dual 1.2GHz G4s, Aluminum PowerBooks and even a couple of eMacs.
Until recently this has been working very well. When the computer is first turned on in the morning, it may take a few seconds, maybe a minute, before the login window will accept your LAN ID and password. It will "shake" if you're logging in too soon. For the most part, folks were willing to put up with this. However, it now seems to be taking longer and longer each morning before one can login.
Also, it is now almost impossible to login after the screen saver has been activated. For two months it's been working fine and now almost no one can authenticate against the screen saver.
And finally, the computers have been set to sleep after one hour of inactivity but after waking a computer it will be impossible to login against the screen saver at all. Pretty much your only option is to login as the local administrator and then log out and have the user log back in from the login window (and not the screen saver).
Well, for obvious reasons, I can't really wander around the halls patrolling for people whose computer has gone to sleep so I can login as the admin and get the login window to come back. None of these issues appeared for the first month we were logging in like this. But it's now happening so often, that I am unable to do any other work but walk around logging myself in as the admin and then logging out again. We have about 150 more people to upgrade and some of them are remote users. We'll need to address this issue before we can start giving them support from across the country. Any suggestions on what settings on the Mac to check or issues with the network or Active Directory would be greatly appreciated. Unfortunately, it is EXTREMELY doubtful I would be able to affect any changes to the Active Directory itself. Even though the Mac support folks are, technically, in IT, we're pretty much ignored and poo-pooed when issues come up... Don't get me started!
-Doug
Until recently this has been working very well. When the computer is first turned on in the morning, it may take a few seconds, maybe a minute, before the login window will accept your LAN ID and password. It will "shake" if you're logging in too soon. For the most part, folks were willing to put up with this. However, it now seems to be taking longer and longer each morning before one can login.
Also, it is now almost impossible to login after the screen saver has been activated. For two months it's been working fine and now almost no one can authenticate against the screen saver.
And finally, the computers have been set to sleep after one hour of inactivity but after waking a computer it will be impossible to login against the screen saver at all. Pretty much your only option is to login as the local administrator and then log out and have the user log back in from the login window (and not the screen saver).
Well, for obvious reasons, I can't really wander around the halls patrolling for people whose computer has gone to sleep so I can login as the admin and get the login window to come back. None of these issues appeared for the first month we were logging in like this. But it's now happening so often, that I am unable to do any other work but walk around logging myself in as the admin and then logging out again. We have about 150 more people to upgrade and some of them are remote users. We'll need to address this issue before we can start giving them support from across the country. Any suggestions on what settings on the Mac to check or issues with the network or Active Directory would be greatly appreciated. Unfortunately, it is EXTREMELY doubtful I would be able to affect any changes to the Active Directory itself. Even though the Mac support folks are, technically, in IT, we're pretty much ignored and poo-pooed when issues come up... Don't get me started!
-Doug
