Our situation calls for several "communal" laptops. Since we are a severely understaffed organization in our IT dept...with 4500 or so users, and about 350 laptops that exists, because of the "communal" laptops, and the fact we are rather understaffed for what we do, we modified the SBFS to be larger than the standard 20MB to allow for all users and then some to be added to the local machines. This worked great...but now we have some users in which it takes anywhere from 5-10 minutes after logging in to Safeboot for the Windows load screen to come up.
We initially had this problem when we had check for autoboot still enabled and it dissappeared after we disabled the check for autoboot. Any of us in our IT dept or help desk have no problem logging on to these machines quickly. We have re-imaged the machines and re-safebooted them...same thing. I have had added a user to my laptop in Safeboot (I usually only have myself in there) and same thing...she had problems. Re-create the users....same problem.
We are using 5.1.7 build 5500.
If anyone can shed anylight on this, it would be greatly appreciated as I have pretty much nailed down that it is not a computer issue but something with Safeboot and the users.
Because there are laptops out there that have several users on them...several of which may or may not ever logged onto that machine before. To be honest, our implementation isn't exactly the best. It was slapped together in order to meet the requirements set forth by a government agency in a short fashion. We had minimal time to actually sit and work with it...and nil for training.
How exactly does autodomain work, as I am not familiar with it at all?
A few things that don't seem to make much sense to me. You have 300 laptops that 4000 users use? If so, what you need need a process for loaning out laptops and assinging user id's to them. Maybe you can remove some accounts for clients who don't ever use the laptop? How is the laptop assigned?
We have a small loaner pool of laptops and a process by which they go about getting them. If the machine isn't leaving the company, we assign the autologon user account to it, if it is, we assign that users id to it.
Yeah...the laptop loaner thing is a source of frustration for us. We have about 30 sites across a pretty diverse geographical region. The IT dept does not control these laptops...they are actually held in filing cabinets and if someone needs one for whatever reason, a manager signs it out to them. These are in the far minority.
The majority of the others are infact shared by more indeterminable number of people for one.
Some organizational information might help you understand further: we are a regional health authority in Canada. Many of our laptops are for home care nurses which make rounds to patients in the patients homes/residences. They connect back to the office for their charting and reporting via EVDO and VPN. While they are encouraged to use the same laptops, it is not always possible. A very small percentage are in fact "communal" laptops in which just anyone can sign out...and the rest are pretty much assigned to users.
We implemented this hastily (I am the first to admit that) and were looking for a relatively painless way to manage users. So that is why we created one group in AD for the general users, threw them all into it, created an AD connector to map them to the Users group...and then added the users group to the machine group.
Only recently after digging deeper into user complaints I came here (it has only ever been a few users...and because it was always the same few people, we never perceived it to be a widespread problem...I guess the rest just accepted the delay as a fact of life) And now that I know the problem...I would like to get this resolved as relatively painlessly, expediantly & risk-free.
autodomain seems like it is certainly the way to go (as I am not about to micro-manage user & machine groups, connectors and OUs.) But I am just curious as to how Autodomain would handle the addition of a new user.