Windows Run Commands – If you need to quickly access one of these Windows services or programs, you can try to just type the following in the Run box, or search for it and then double click it to run.
Program – Run Command
Accessibility Controls – access.cpl
Accessibility Wizard – accwiz
Add Hardware Wizard – hdwwiz.cpl
Add/Remove Programs – appwiz.cpl
Check Windows Updates – wuaucpl.cpl
Calculator – calc
Certificate Manager – certmgr.msc
Character Map – charmap
Check Disk Utility – chkdsk
Command Prompt – cmd
Component Services – dcomcnfg
Computer Management – compmgmt.msc
Create a shared folder Wizard – shrpubw
Date and Time Properties – timedate.cpl
Device Manager – devmgmt.msc
Direct X Troubleshooter – dxdiag
Disk Cleanup Utility – cleanmgr
Disk Defragment – dfrg.msc
Disk Partition Manager – diskmgmt.msc
Driver Verifier Utility – verifier
Event Viewer – eventvwr.msc
Files and Settings Transfer Tool (Migration Wizard) – migwiz
File Signature Verification Tool – sigverif
Group Policy Management Console – GPMC
Local Group Policy Editor – gpedit.msc
Internet Properties inetcpl.cpl
IP Configuration (Display Connection Configuration)
IP Configuration (Display DNS Cache Contents)
IP Configuration (Delete DNS Cache Contents)
IP Configuration (Release All Connections)
IP Configuration (Renew All Connections)
IP Configuration (Refreshes DHCP & Re-Registers DNS)
IP Configuration (Display DHCP Class ID)
IP Configuration (Modifies DHCP Class ID)
Local Security Settings
Local Users and Groups
Malicious Software Removal Tool – mrt
Microsoft Diskpart – diskpart
Microsoft Management Console – mmc
Microsoft Paint – mspaint
Microsoft Syncronization Tool – mobsync
Mouse Properties – main.cpl
ODBC Data Source Administrator – odbccp32.cpl
On Screen Keyboard – osk
Performance Monitor – perfmon.msc
Power Configuration – powercfg.cpl
Regional Settings – intl.cpl
Registry Editor – regedit
Remote Desktop – mstsc
Resultant Set of Policy – rsop.msc
Security Center – wscui.cpl
Services – services.msc
Shared Folders – fsmgmt.msc
Sounds and Audio – mmsys.cpl
Legacy System Configuration Utility – msconfig
System File Checker Utility ( Scan Immediately ) – sfc /scannow
System File Checker Utility ( Scan Once At Next Boot ) – sfc /scanonce
System File Checker Utility ( Scan On Every Boot ) – sfc /scanboot
System File Checker Utility ( Return to Default Settings) – sfc /revert
System File Checker Utility ( Purge File Cache ) – sfc /purgecache
System File Checker Utility ( Set Cache Size to Size x ) sfc /cachesize=x
System Information – msinfo32
System Properties – sysdm.cpl
Task Manager – taskmgr.exe
Volume Control – sndvol
Windows Firewall – WF.msc
Windows Magnifier – magnify.exe
Windows Management Infrastructure – wmimgmt.msc
Windows Picture Import Wizard (Need camera connected) – wiaacmgr
Windows System Security Tool – syskey
Windows Script host settings – wscript
Windows Version ( shows your windows version ) winver
Here is a list of new services in Windows 8 and Server 2012 that were not present in Windows 7 or Server 2008. I tried searching for this information online and could not find a dedicated list anywhere of just new services, so I figured I would post one in case someone else was curious.
1. Background Tasks Infrastructure Service – Coordinates execution of background work for WinRT (Metro) applications.
2. Claims to Windows Token Service – Service to convert claims based identities to windows identities. (Not installed by Default)
3. Device Association Service – Enables pairing between the system and wired or wireless devices.
4. Device Install Service – Enables a computer to recognize and adapt to hardware changes with little or no user input. Stopping or disabling this service will result in system instability. (This seems like it is the same as the old Plug N Play service.)
5. Device Setup Manager – Enables the detection, download and installation of device-related software. If this service is disabled, devices may be configured with outdated software, and may not work correctly. (Device Driver Automatic Update)
6. DS Role Server -This service hosts the DS Role Server. (This service is used by Domain Controllers in place of DC Promo.)
7. Hyper-V Data Exchange Service. Provides a mechanism to exchange data between the virtual machine and the operating system running on the physical computer.
8. Hyper-V Guest Shutdown Service – Provides a mechanism to shut down the operating system of this virtual machine from the management interfaces on the physical computer.
9. Hyper-V Heartbeat Service – Monitors the state of virtual machines by reporting a heartbeat at regular intervals. This service helps you identify running virtual machines that have stopped responding.
10. Hyper-V Remote Desktop Virtualization Service – Provides a platform for communication between the virtual machine and the operating system running on the physical computer.
11. Hyper-V Time Synchronization Service – Synchronizes the system time of this virtual machine with the system time of the physical computer.
12. Hyper-V Volume Shadow Copy Requestor – Coordinates the communications that are required to use Volume Shadow Copy Service to back up applications and data on this virtual machine from the operating system on the physical computer.
13. Local Session Manager – Core Windows Service that manages local user sessions. Stopping or disabling this service will result in system instability.
14. Microsoft Account Sign-In Assistant – Enables user sign-in through Microsoft account identity services. If this service is stopped, users will not be able to logon to the computer with their Microsoft account.
15. Network Connected Devices Auto-Setup – Network Connected Devices Auto-Setup service monitors and installs qualified devices that connect to a qualified network. Stopping or disabling this service will prevent Windows from discovering and installing qualified network connected devices automatically. Users can still manually add network connected devices to a PC through the user interface. (sounds like more UPNP Crap)
16. Network Connectivity Assistant – Provides DirectAccess status notification for UI components.
17. Optimize Drives – This service is new for Windows 8 and it is a renamed version of the Disk Defragmenter Service.
18. Printer Extensions and Notifications – This service opens custom printer dialog boxes and handles notifications from a remote print server or a printer. If you turn off this service, you won’t be able to see printer extensions or notifications.
19. Sensor Monitoring Service – Monitors various sensors in order to expose data and adapt to system and user state. If this service is stopped or disabled, the display brightness will not adapt to lighting conditions. Stopping this service may affect other system functionality and features as well.
20. Spot Verifier – Provides Disk Corruption Spot Verification Capabilities.
21. Still Image Acquisition Events – Launches applications associated with still image acquisition events.
22. System Events Broker – Coordinates execution of background work for WinRT application. If this service is stopped or disabled, then background work might not be triggered. (Most likely Live Tiles use this service to update.
23. Time Broker – Coordinates execution of background work for WinRT application. If this service is stopped or disabled, then background work might not be triggered. (Also for Live Tiles and Updating Modern Apps.)
24. Touch Keyboard and Handwriting Panel Service – Enables Touch Keyboard and Handwriting Panel pen and ink functionality. (similar to the old Tablet PC Input Service.)
25. All User Install Agent – Install AppX Packages for all authorized users.
26. Windows Connection Manager – Makes automatic connect/disconnect decisions based on the network connectivity options currently available to the PC and enables management of network connectivity based on Group Policy settings.
27. Windows Store Service – Provides infrastructure support for Windows Store.This service is started on demand and if disabled applications bought using Windows Store will not behave correctly.
Thats 27 more services that Windows added for Windows 8.
VMware file corruption error example
I have been testing Windows8 and its Native Hyper-V Client against VMWare Workstation 9.0.1 running on Windows 7 Ultimate and have seen Workstation Cause many major problems. I am just going to jump in and explain the various problems that I have run into with VMware that have not been an issue with my Hyper-V Virtual Servers running on Windows 8.
- Often, VMware Workstation virtual machines in my lab have experienced intermittent network issues where shared folders do not stay connected. I have had to restart Windows Server Backup to Network Drives several
times with many “an unexpected network error occurred” messages killing my backups.
- Hyper-V has an outstanding feature called Dynamic Memory as well as Minimum and Maximum memory which are great for allowing more than 2 Virtual Machines to always run in the background. VMWare Workstation does not have an option to configure Dynamic Memory.
- Another major problem that is a showstopper is when VMware pops up Fatal Error messages (shown below) that are
complaining of File Corruption with different error messages that have caused my virtual servers to crash, often leading to recovery from snapshots or server backups. See the image for an example of these annoying errors!
- Perhaps most importantly, Hyper-V is built into Windows 8 so I don’t need to install any heavy applications on
my windows 8 computer which end up fighting with the operating system for resources and this ultimately leads to a much lighter feeling of the Operating System with Hyper-V compared to Windows 7 with VMWare workstation chugging away.
Now this is only my opinion, and I am curious if anyone feels the opposite and after experiencing both can honestly say that they prefer using VMware Workstation to Native Hyper-V on Windows 8. The important distinction here is Native Hyper-V on Windows 8, I am not talking about the older version of Hyper-V that was available on Server 2008. It is the Windows 8 version of Hyper-V that I prefer. Also, I tested Workstation on Windows 7 and Windows 7 does not run as smoothly as Windows 8, I know a lot of people that prefer Windows 7, but after comparing the two honestly, Windows 8 runs much smoother and faster than Windows 7 in my personal tests.
There is one place where VMware Workstation does top Hyper-V so far and this is copy and paste abilities. It is easy to copy a file or text from your host machine and paste it into your Guest Virtual Machine, but in Hyper-V it is not as easy. Hyper-V only has a menu title at the top of the VM window that says Clipboard, inside this is only two options… Type clipboard text and Capture Screen. They are seriously lacking a file copy and paste option. Microsoft explains that you can use a mapped drive inside the virtual machine to do file transport between Guests and the Host, but it would be much easier to be able to just copy a file from the host and paste it into the guest like I have gotten used to doing in VMware.
Remoting in PowerShell 2.0 can be enabled by just running the following cmdlet in an elevated PowerShell prompt
Powershell Remoting uses port 5985 for HTTP or 5986 for HTTPS. By default, remoting takes place over HTTP utilizing Windows remote shell Management or WS-Man so if you run the command winrs -r:ComputerName:5985
in an ordinary command prompt it is similar to using Powershell remoting. Windows Remote Management service needs to be running.
To test Powershell remoting to a certain computer you can issue the following command: Enter-PSSession -ComputerName localhost
If remoting is functional you will see the prompt change to :
[computername]: PS C:
Note that these simple commands will only work in a domain environment if you are a local administrator of the computer you are controlling or if you are a domain admin. Workgroup joined computers require a few more steps before being able to create remoting sessions. For more info on Powershell remoting you can read the free book “A layman’s guide to PowerShell 2.0 Remoting by Ravikanth Chaganti and Jan Egil Ring.
I have been spending most of my time getting used to System Center Configuration Manager 2012 sp1 and there is so much to learn about this software. It is capable of managing up to 400,000 computers when you use the default settings. It is a monster infrastructure application, and really is the ultimate in IT Pro System Administration. The install process is not as complicated as it was in prior versions, but it took me a whole night to take care of all the prerequisites on a brand new Server 2012 Virtual Machine. I set it up as a Stand-Alone site since I will be using it in a Lab Domain with only about 20 clients and servers. I extended my Active Directory schema, and installed WDS, WSUS, and SQL server 2012 sp1 before the installation would continue. The main problems that I noticed when trying to install Configuration Manager was that an error kept popping up telling me that the SQL Server service was not running as a domain user.
If you need to configure the SQL server service to run as a domain user, you need to open up SQL Server Configuration Manager and from there you can right click on the SQL server service and change its logon user account. Once you get it installed, you are going to want to install ConfigMgr agents on whatever clients you are going to be managing. Here is how to install the agents using Group Policy. First of all, Config Mgr has three important files that are used for getting the agents installed on your clients. They are in automatically shared folders created by COnfiguration Manager upon installation. The important share is actually located in C:Program FilesMicrosoft Configuration ManagerSMS_[yoursitename]. In this share is many folders, and the file CCMsetup.msi is located under BINI386. There is also a CCMSetup.exe file located in the same folder. These files may also be located in the CLIENT folder, but in my case, ccmsetup.msi was not there. The third file is client.msi and should not be invoked directly, (it is actually invoked automatically when you run CCMsetup.exe).