Comment Re:What protocol for remote access? (Score 1) 780
WinRM - powershell remoting tunneled over https.
WinRM - powershell remoting tunneled over https.
But I strongly feel that if the Linux folks would take a step back and acknowledge that it's no longer 1970, they'd see that have programs set up to pass objects around instead of text can be hugely beneficial.
The advantage here being...? It sounds like a cool feature, but what would I be doing where I would actually want to have object oriented programming in my shell?
Ok, how about:
Boss comes to you and says something like:
"Can you tell me what version of windows is running on all of our machines, and what service pack they are on?"
"...and can I have that as a CSV?"
You:
gc machines.txt | % { gwmi win32_operatingsystem -computer $_ } | select __SERVER,Name,OSArchitecture,ServicePackMajorVersion,ServicePackMinorVersion | export-csv
Boss: Actually, can I have that in html? I need to put that up in a web site
You: OK..here you go
gc machines.txt | % { gwmi win32_operatingsystem -computer $_ } | select __SERVER,Name,OSArchitecture,ServicePackMajorVersion,ServicePackMinorVersion | convertto-html > report.html
I find that you can do things in PS that are a pain in bash (e.g. get a list of processes started within the last hour)
It doesn't help that most of the supposed IT people that I interview are woefully inept when it comes to anything above desktop support work. Even the staple (Windows) exam questions like "What are the 5 FSMO roles" or "How would you recover a failed domain controller" or even "What are the stages of name resolution" usually result in blank stares. Once you start getting into more complex questions such as the pros and cons of running different systems in virtual environments they mostly just give up entirely.
A lot of these people are contractors that are sent by reputable agencies as "the best they have to offer" and are asking £300-£350/day or more. Frankly I'm amazed that the unemployment rate for them isn't much higher, I can only assume that most of the time they either don't have to interview or get interviewed by someone just a little worse than they are.
Let me see...
FSMO roles:
PDC emulator
Schema master
Domain naming master
RID master
Infrastructure master
Recovering a failed domain controller?
I'm going to assume it's a replica DC and connected by a reasonably high bandwidth link, and your NTDS database isn't too big, and you have other functioning domain controllers
1. Seize any FSMO roles hosted by this DC (probably also worth checking that it's not the only DC configured for DNS scavenging, etc and move those roles well)
2. perform metadata cleanup (using ADUC if 2K8, or ntdsutil if 2K3 or below)
3. repair machine
4. reinstall windows + required patches
5. dcpromo as replica
6. wait for replication
7. ???
8. profit
Having deployed both in an enterprise, I can say that if you're trying to automate imaging, go with Bladelogic. If you're trying to automate package deployment/policy, go with HPSA. Bladelogic has a great feature - it has a custom PXE server that keeps track of the state of the OS install, and changes the boot so that you can set your servers to network boot, and once they're installed, Bladelogics PXE server will make it us the HDD. This is fantastic, compared to HPSA where you need to dink around to make things happy.
ymmv
HPSA does this too, you just need the MBC extension...
A committee takes root and grows, it flowers, wilts and dies, scattering the seed from which other committees will bloom. -- Parkinson