This content has been marked as final. Show 14 replies
Can you please explicitly state old and new version numbers?
New Build Number is 5600
Old Build Number was 5200
Hope this helps
no, there's no way of expanding it other than something like a disable/enable or an eboot.
why would you need such a large SBFS though?
We have over 1500 laptops which we wanted any of our 12,000 users to be able to log onto. Therefore we needed the largest size of local database.
thats really bad security ;-)
You know the sync times will be extremely long, probably for ever, and the network load! wow, it's going to be immense, your WAN/LAN and your server are going to have to be extraordinarily capable to cater for this.
I know it seems "easy" just to assign everyone to every machine, but it's really bad security. I mean, how many people REALLY use each machine?
Within our organisation we have several hospitals, clinics, etc etc where the turn around of staff is immense. At the moment we use asset tag and password but sometimes staff forget or setup passwords and forget to relay the info on, hence AD integration would stop this from happening.
I rather think this is a design flaw. I wish EEPC pre-boot would mimic and follow Windows cached credentials. Automatically.
We have a number of Security logons which can log onto any machine within the organisation. But in effect if you dont tie the user into a group against their own machine, the user can log onto any other machine in that group with their username and password.
Secure? Not Really..... sad
There you have it - Windows only allows you to logon as a new user if you are online, it DOES NOT allow previously unknown users to login while offline.
There's also no way to pre-cache users with Windows.
As for mimicking Windows cached credentials, that's what the Autodomain script does? It will automatically add users on the fly as they use the machine?