For my fellow sysadmins

[thrun]

http://technet.microsoft.com/en-us/sysinternals/bb897557.aspx

This is a handy little toy for seeing all the important info of whatever machine you are on.   I'll probably be putting it out on my production servers at the end of the week.   

[Sultress]

We use this, very handy.  It's set to all our employee's wallpaper.  Only bad thing is it's a snapshot and not necessarily current.  (usually is though)

[Snackcakes]

 we use these on ALL of our lab and classroom machines. I think about 800 machines. It works great.

[Redbear8]

Yeah, we use this as well. It's really handy for a quick peek so long as you keep it current.

[Snackcakes]

seriously guys... the wolverines consulting group.. think about it

[Redbear8]

Our Logo!

"We'll solve your problems or mangle you! 100% Satisfaction guaranteed!"

[thrun]

Our Logo!

"We'll solve your problems or mangle you! 100% Satisfaction guaranteed!"

We'll solve your problems or get one of our cougars to do it!

[thrun]

Also, if any of you care I decided to just run the exe and import the config we want of a share on our managment server.  Then I createda  bat  in the sysvol on the DC's and added it to the log on script for systems group.  That way only we are getting the information, since no one else really needs it for any reason.

I don't have enough to do this week incase you were wondering.

[Snackcakes]

Also, if any of you care I decided to just run the exe and import the config we want of a share on our managment server.  Then I createda  bat  in the sysvol on the DC's and added it to the log on script for systems group.  That way only we are getting the information, since no one else really needs it for any reason.

I don't have enough to do this week incase you were wondering.

good then tell my why my virtual machine keeps blue screening and getting stuck in a boot loop after I sysprep it.  I am building an image on a vm, because it's nice with the snapshots - but for some reason after I sysprep it goes to shit.

[thrun]

Also, if any of you care I decided to just run the exe and import the config we want of a share on our managment server.  Then I createda  bat  in the sysvol on the DC's and added it to the log on script for systems group.  That way only we are getting the information, since no one else really needs it for any reason.

I don't have enough to do this week incase you were wondering.

good then tell my why my virtual machine keeps blue screening and getting stuck in a boot loop after I sysprep it.  I am building an image on a vm, because it's nice with the snapshots - but for some reason after I sysprep it goes to shit.

No clue,  I don't use the snap shots in VMware.  We have one sysp'd machine that we just coppied the actual data file that vmware creats from.  I just create a new vmware machine with the same disk configuration, then copy the origional file that we have over the new one that was created. 

The dude that created the file quit a half a year ago.