I've received the error several times on Windows 7 Workstations and Laptops where it loses trust with the domain controller, and I know how to fix it, but why does it do that?
If you have one computer, is it possible to simulate having multiple computers - each being tied to it's own monitor/keyboard/mouse?
For example: Assuming I have a single computer running two instances of DamnSmallLinux using virtualbox, and it's connected to two sets of monitors, keyboards, and mice, can both users simultaneously use their respective linux instance?
Use case: You're teaching kid's how to use computers. You have 10 kids but only one computer, but you do have extra peripherals. You hoped you could just buy 10 raspberry pi's but then a freak manufacturing error delayed production, so your trying to plan a way to produce the maximum number of workstations on the minimum amount of hardware.
Related to this but different enough so that I think it deserves its own question.
I'm the sysadmin of a small business, and by 'sysadmin', I mean 'by the seat of my pants' (still in university, not a lot of real-world experience, etc). I'm not ignorant, just inexperienced.
Anyway - we've got about 10 office employees whose computer usage consists mostly of using a web browser, pulling up Word occasionally, and interacting with our company's database through FileMaker. Our current batch of workstations are 5-year-old Dell E520s that literally never get shut down. I'm not worried about hard drives failing - by and large, most important files are saved on a networked drive - the big deal is just plain old energy efficiency. We're a small business, and I wrack my brains every day trying to figure out ways to shave a few dollars here and there from our overhead, and shutting the workstations down at 5p and firing them all back up at 9a seems like an easy way to do that (not to mention the tangible performance benefits that come from restarting Windows XP, as opposed to letting 10 tabs of FireFox leak memory all night long :P).
This may be an extremely stupid question, but what do you all think?
Is there a good way to solve the following?
- Domain has an AD security group called "Workstation Administrators", for users that should not be domain admins, but should have local administrative control over all workstations in the domain
- Technicians frequently forget to manually add this group after joining a PC to the domain and wastes time later on having to diagnose, go back and do it
Anybody know an automatic way of adding this group, or running a script on domain-join? Or would we need to run an automated audit process every so often after the fact?
When removing and re-joining a workstation from and to AD, are there any drawbacks from dis-joining it from AD, without deleting the AD object, and re-joining it back? Please detail.