Check System Uptime

net statistics workstation
net statistics workstation | find "Statistics since"
systeminfo
systeminfo| find "System Boot Time"

AD Query

Locked Out Users - Displays all the user accounts that are locked out
(&(&(&(&(objectCategory=person)(objectClass=user)(lockoutTime:1.2.840.113556.1.4.804:=4294967295)))))
 
Dial In Access - Displays all the user accounts with Dial In Access
(&(&(&(&(objectCategory=person)(objectClass=user)(msNPAllowDialin=TRUE)))))
 
Disabled User Accounts - Displays all the user accounts that are currently disabled
(&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=2))
 
Non Expiring Accounts - Displays all the user accounts that are set to not expire
(&(objectCategory=person)(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=65536))
 
Active Accounts - Displays all the users account that are active
(&(&(objectCategory=person)(objectClass=user)(!userAccountControl:1.2.840.113556.1.4.803:=2)))
 
 Hidden Mailboxes - Displays all accounts with hidden Mailboxes
(&(objectCategory=person)(objectClass=user)(msExchHideFromAddressLists=TRUE))
 
 Windows XP Computers - Displays all computers running Windows XP
(&(&(&(&(&(&(&(objectCategory=Computer)(operatingSystem=Windows XP Professional)(operatingSystemServicePack=Service Pack 3))))))))
 
Vista Machines – Displays all computers running Windows Vista
(&(&(&(&(&(&(sAMAccountType=805306369)(objectCategory=computer)(operatingSystem=Windows Vista*)))))))
 
Vista Machines – SP1
(&(&(&(&(sAMAccountType=805306369)(objectCategory=computer)(operatingSystem=Windows Vista*)(operatingSystemServicePack=Service Pack 1)))))
 
All Computers - Displays all computers
(sAMAccountType=805306369)
 
Windows Server 2000 - Displays all computers running Windows Server 2000 (not including DC’s)
(&(&(&(&(&(objectCategory=Computer)(operatingSystem=Windows 2000 Professional))))))
 
Windows Server 2003 - Displays all computers running Windows Server 2003 (not including DC's)
 (&(&(&(samAccountType=805306369)(primaryGroupID=516)(objectCategory=computer)(operatingSystem=Windows Server 2003*))))
 
Windows Server 2008 - Displays all computers running Windows Server 2008 (not including DC's)
(&(&(&(&(samAccountType=805306369)(!(primaryGroupId=516)))(objectCategory=computer)(operatingSystem=Windows Server 2008*))))
 
All Windows Server Domain Controllers - Displays all computers that are Domain Controllers
(&(&(&(sAMAccountType=805306369)(useraccountcontrol:1.2.840.113556.1.4.804:=67117056))))

My Document Folder Redirection

My Document Folder Redirection

Check in these two places

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders

VMware vSphere 4 ( ESXi 4) on Windows 7 PC by VMware Workstation 7

Basic Requirements for VMware vSphere 4( ESXi 4) on a PC

1) Minimum 2GB RAM should be allocated for ESXi 4 virtual machine. So, you must have minimum 3GB RAM on computer.

2) Hardware virtualization should be available and enabled on motherboard.

How to Confirm Virtualization Technology is Enabled or Disabled?

1) If your processor is Intel, then you can use this free utility to confirm the result which operating system is sensing.

Download Intel tool to confirm virtualization technology

The result of this utility brings a screen as shown below,

2) For AMD Processors download the below utility.

3) Microsoft Tool to check hardware virtualization Technology ( VT)

Download the free tool from Microsoft here.

Source:

http://www.sysprobs.com/vmware-vsphere-4-esxi-4-windows-7-vmware-workstation-7-pc

http://www.sysprobs.com/disable-enable-virtualization-technology-bios

How to install VMware VSphere ESXi 4 on a desktop PC

Trying to figure out how to install VMWare Vsphere ESXi 4.0 on a home desktop computer but now sure how? Neither was I but I finally figured it out and I’ll tell you how!

Over the last year, I’ve been getting very involved in VMware ESX installations and rollouts at work. It started with doing several hundred P2V’s (physical machine to virtual machine conversions) then onto the server side and actually configuring the servers. We started with ESX 3.5 then upgraded to ESXi 4.0 which is now known as VSphere.

I took a couple of VMware training classes and realized that there was a lot of capabilites in VSphere that we weren’t using at my company. Unfortunately, since it was a production environment, tinkering and experimenting on the ESX clusters at the office wasn’t an option. I’m the type of person that when I get into a technology, I want to know as much about it as possible. It also helps to learn as much as possible as it makes you more valuable at work and to potential (higher paying) employers.

RESEARCH

My research began to find out what it would take to build a VMware VSphere ESXi 4.0 server at home.

A quick google search showed it was very possible to build a home ESX server, but unlike Windows servers there were very specific hardware requirements. Even tougher, VMware doesn’t list what desktop class hardware you can run it on since they don’t officially support running ESX on desktops. There are a couple of sites out there like UltimateWhiteBox.com that list various components that people have reported success in using, but obviously there is a huge range of possible hardware combinations out there on home machines, so a lot is not covered. The other issue is that it seems that the sites aren’t updated that often, if at all anymore.

Continuing my research, I looked into what processors were compatibile with ESXi 4 and settled on the Intel Quad Core. I specifically wanted a quad core processor since I was going to have several virtual machines running on it and didn’t want the processors pinned at 100% utilization from having too little cpu. I also wanted a lot of RAM for the same reason.

I was debating whether to buy all the components and build the machine myself, but every time I started pricing out components, I realized it would cost me the same or more than just buying an off the shelf desktop pc plus all the time involved in building it.

I ultimately settled on buying an HP Pavilion with an Intel Core i7 and 8gb of RAM. This would be a very solid machine at a decent price. I headed over toAmazon.com to see what they had since I could get it tax free and with free shipping.

THE BUILD

The machine arrived and I was impressed with the look. It looked like it was made to be a server with smooth glossy paint and even a cool arctic blue glowing power button. I gleefully started out trying to install ESX. First I tried ESX 3.5 and that failed since it couldn’t find my SATA controller. Next I tried ESXi 3.5 with the same result. I was getting worried but crossed my fingers and installed ESXi 4.0 and it worked! The only hiccup was that it couldn’t see the onboard network controller, which I knew would probably happen as VMware generally only recognized broadcom and Intel based NICs and the HP came with an onboard Realtek NIC.

I was bummed that I wouldn’t get to start playing immediately but was still happy that it was going to work. I headed back over to Amazon and picked up an Intel Gigabit Ct Desktop adapter for about thirty bucks. Two days later it showed up and I popped it into the machine. *Presto!* I have a fully functioning ESXi 4 VSphere server! **YAY!!**

After creating a couple of test VM’s and contemplating what type of home virtual universe I should start building, it occurred to me that the single drive in the Pavilion was not going to be big enough. I then started having my usual internal debate where my geek side fights with my cheap side over whether to buy larger drives or cheaper drives. I found a good compromise in the $119 Western Digital 2TB Caviar Green hard drives. They have an outstanding amount of storage and variable speed which allows them to spin down to a slower speed during the day while I’m away but ramp back up to full speed when I’m banging away on them doing Windows 2008 server installs.

I bought two of the drives and in another two days they arrived. I popped them in (replacing the original drive that came with the Pavilion) and reinstalled ESXi 4. Luckily the VMware installation is only about 15 minutes total. The drives worked like a charm out of the box and are drop dead silent which made me happy since I hate having the jet engine like whir of multiple hard drives in the background while I try to work.

THE RESULT

I am happy to report that over a month later, this machine is rock solid. I have two workstation VM’s and two server VM’s running 24 x 7 on it and haven’t had a hiccup. I’ve retired the hardware that my Windows Home Server was on as I’ve successfully virtualized it. I’ve found so many cool uses for it that I hadn’t even thought of before. For example, I loaded up a generic Windows XP vm that I remote control from my Apple iPad over wifi. I have another that I use when I am downloading from suspicious websites that may contain malware. When I’m done with the download and have scanned it for viruses, etc, I just power off the vm and restore it from a pristine image.

I can’t say enough about how happy this setup has made me (I know, I know, super geek)!

WHAT YOU’LL NEED

Here’s my final shopping list for this setup:

- HP Pavilion with an Intel Core i7 and 8gb of RAM
- Intel Gigabit Ct Desktop adapter
- Western Digital 2TB Caviar Green hard drives

Let me know if you’ve had success with a similar configuration or have questions about setting up your own by leaving a comment below.

Source:

http://www.gettingolderandwiser.com/technology/how-to-install-vmware-vsphere-esxi-4-on-a-desktop-pc.html

Command Lines

AD Domains and Trusts
domain.msc

Active Directory Management
admgmt.msc

AD Sites and Serrvices
dssite.msc

AD Users and COmputers
dsa.msc

ADSI Edit
adsiedit.msc

Authorization manager
azman.msc

Certification Authority Management
certsrv.msc

Certificate Templates
certtmpl.msc

Cluster Administrator
cluadmin.exe

Computer Management
compmgmt.msc

Component Services
comexp.msc

Configure Your Server
cys.exe

Device Manager
devmgmt.msc

DHCP Managment
dhcpmgmt.msc

Disk Defragmenter
dfrg.msc

Disk Manager
diskmgmt.msc

Distributed File System
dfsgui.msc

DNS Managment
dnsmgmt.msc

Event Viewer
eventvwr.msc

Indexing Service Management
ciadv.msc

IP Address Manage
ipaddrmgmt.msc

Licensing Manager
llsmgr.exe

Local Certificates Management
certmgr.msc

Local Group Policy Editor
gpedit.msc

Local Security Settings Manager
secpol.msc

Local Users and Groups Manager
lusrmgr.msc

Network Load balancing
nlbmgr.exe

Performance Montior
perfmon.msc

PKI Viewer
pkiview.msc

Public Key Managment
pkmgmt.msc

QoS Control Management
acssnap.msc

Remote Desktops
tsmmc.msc

Remote Storage Administration
rsadmin.msc

Removable Storage
ntmsmgr.msc

Removalbe Storage Operator Requests
ntmsoprq.msc

Routing and Remote Access Manager
rrasmgmt.msc

Resultant Set of Policy
rsop.msc

Schema management
schmmgmt.msc

Services Management
services.msc

Shared Folders
fsmgmt.msc

SID Security Migration
sidwalk.msc

Telephony Management
tapimgmt.msc

Terminal Server Configuration
tscc.msc

Terminal Server Licensing
licmgr.exe

Terminal Server Manager
tsadmin.exe

UDDI Services Managment
uddi.msc

Windows Mangement Instumentation
wmimgmt.msc

When opening the Word document users are getting error “Word cannot start the converter mswrd632.wpc” or “Cannot load Word for Windows 6.0 files”

When opening the Word document users are getting error “Word cannot start the converter mswrd632.wpc” or “Cannot load Word for Windows 6.0 files”


Problem: - When attempting to open a Word document, users are getting one of following error
1) Word cannot start the converter mswrd632.wpc
2) Cannot load Word for Windows 6.0 files
Cause: - This issue may be started happening after you applied following security update. You may be trying to open a file has the ".doc" file name extension, but the content is a plain text file or another kind of file that is not a Microsoft Word binary file.


Resolution: - The registry fix for this issue is already provided in the KB 973904. Following solution is the updated solution which is provided by Microsoft Word Team. You can use the following steps for the resolution.
Update:- Fix-IT solution for this registry changes is released. Check KB973904
WARNING : If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this issue, an affected user can unregister the mswrd632 converter by editing the registry as follows:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey:
2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools
\Text Converters\Import\MSWord6.wpc
c. On the Edit menu, click Delete.
d. Click Yes.
e. Exit Registry Editor.
This change will effectively unregister the converter and disable it for third-party applications and for Microsoft Office. Microsoft Office will use its own text converters to open these kinds of files.

==============================================================================================
In case you want to re-enable the converter, you can add an AllowConversion registry entry with a DWORD value of 1. After you set this registry key value to 1, third-party applications can load the Word 6.0/95 for Windows and Macintosh to RTF converter. Please be aware that setting this registry key removes the protection that was added by this security update. Therefore, it should be done only when you trust the source of the files that are loaded by this converter. You can also disable this converter by setting the registry key value to 0.
To do this, follow these steps:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate and then click the following registry subkey. Or, create it if it is not present.

For 32-bit versions of Windows
2. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
\CurrentVersion\Applets\Wordpad
c. For Microsoft Windows on Windows 64 (WOW) mode
HKEY_LOCAL_MACHINE\Software\Wow6432Node\microsoft
\Windows\CurrentVersion\Applets\Wordpad
d. On the Edit menu, point to New, and then click DWORD Value.
e. Type AllowConversion for the name of the DWORD, and then press ENTER.
f. Right-click AllowConversion, and then click Modify.
g. In the Value data box, type 1, and then click OK.
h. Exit Registry Editor.