To export a list of all computers and non domain controller servers in an Active Directory OU, use dsquery.exe. For example, to export all computers in mydomain.com’s servers OU to machines.txt :
To export a list of all computers and non domain controller servers in an Active Directory OU, use dsquery.exe. For example, to export all computers in mydomain.com’s servers OU to machines.txt :
You can temporarily enable Backup Exec debug logging by adding the -debug start parameter to the Backup Exec Remote Agent for Windows Servers service. This is a temporary setting that will be reset when the services are cycled or at the next server reboot. To enable debug logging permanently, see the second section that details editing the reqistry.
3. Select and right-click on the Backup Exec Remote Agent for Windows Servers service, and then select Properties
4. In the Startup Parameters box, type -debug. Click Start in the Properties page to start the service. Click OK
2. Run REGEDIT.EXE
3. a. Backup Exec 10d or below: Browse to HKey_Local_Machine\Software\VERITAS\Backup Exec\Engine\Logging
5. Quit the registry editor
6. Start the Backup Exec for Windows Servers services
I have an Active Directory domain service account that has permissions to a share on our SAN that will host IIS web site content. I needed to allow IIS to access the share via the service account. Here’s how to do it in IIS 7.0 on Windows Server 2008:
To completely disable DEP in Windows Server 2003, perform the following with administrative credentials:
1. Open Windows Explorer
2. Tools > Folder Options > View
3. Uncheck Hide Protected operating system files (Recommended) and Hide extensions for known file types
4. Click apply > OK
5. Browse to C:\
6. Right click on boot.ini, select properties and ensure the “read-only” tab is unchecked and click OK
7. Edit boot.ini
8. Modify the /noexecute=
For example, set /noexecute=AlwaysOff to disasble DEP entirely
10. Right click on boot.ini, select properties and ensure the “read-only” tab is checked and click OK
11. Reboot the computer
To export a backup copy of your IIS 7.0 configuration on a Windows 2008 Server:
Open Server Manager
Expand Roles – Web Server (IIS) – Internet Information Services (IIS) Manager
Highlight the web server name
From the Management category, double click Shared Configuration
Under Actions, select Export Configuration. Accept or change the default export path of C:\Windows\system32\inetsrv\config\export
Click the Connect As button, and enter administrative credentials. If the server is a domain member, you may need to enter your credentials in the format domain\username or username@domain.com
Enter the encryption keys password twice and press OK
You should now have three files in the C:\Windows\system32\inetsrv\config\export directory: administration.config, applicationHost.config, and configEncKey.key. Save the files in a safe place.
To backup your IIS 7.0 configuration on a Windows 2008 Server, you just need to make a copy of the \windows\system32\inetsrv\config directory (and subdirectories) and save it in a safe location.
You can also use the appcmd.exe utility to create the backup via the command line. The syntax to create a backup is:
%windir%\system32\inetsrv\appcmd.exe add backup “Backup Name”
to restore the backup, the syntax is:
%windir%\system32\inetsrv\appcmd.exe restore backup “Backup Name”
to remove a backup, the syntax is:
%windir%\system32\inetsrv\appcmd.exe delete backup “Backup Name”
For additional details on appcmd.exe see Bill’s IIS blog, or check out Mike’s IIS 7.0 Server-side blog for information on backing up and restoring IIS 7.0 shared configuration.
I have a backup script that runs on a Windows 2003 server that requires Novell client authentication. Here’s how to authenticate to eDirectory via the command line, which means it’s scriptable! The syntax is:
I ran across Claus’s link to the makeuseof.com article that shows how to run Microsoft’s Remote Desktop Connection program as a portable application from a USB drive.
This lead me to think about how this could be of value in my environment. I frequently hop from server to server using Microsoft’s Terminal Services client, mstsc.exe, which is built into Windows XP, Windows 2003 and newer operating systems.
The clicking sound that Windows plays when you click on a link in Internet Explorer or open a folder in Windows Explorer can get annoying.
Here’s how to disable the sound in Windows XP:
Here’s how to disable the sound in Windows Vista:
You should no longer hear the clicking noise when you select links in Internet Explorer or open directories in Windows Explorer.
Msizap is a command-line tool that can delete the configuration data that Windows Installer maintains for products that it installs, including the directories, files, registry subkeys, and registry entries in which Windows Installer stores configuration data.
Running msizap.exe with the G parameter removes orphaned cached Windows Installer data files for all users. Running this command on an old Windows XP machine allowed me to reduce the size of the C:\Windows\Installer directory from 3.6GB down to 875MB.
This computer had so many orphaned files due to the constant installation and uninstallation of software such as Java, Flash, Acrobat Reader, and other utility software over the years. Yes, orphaned files persist on your hard drive despite following proper uninstall procedures.
To run msizap, login to the machine as an administrative user and launch a command window. Navigate to the directory that contains msizap.exe, then type the following command:
msizap !G
The G option removes the orphaned cache files, the exclamation point forces a ‘yes’ response to any prompt.
While removing orphaned files should not have any negative impact on your Windows installation, be aware that msizap is a powerful tool that can cause problems if used incorrectly.
Msizap can be downloaded as a part of the Microsoft Windows Server 2003 Support Tools or the Windows Installer CleanUp Utility. I was unable to find the Windows Installer CleanUp Utility by searching Microsoft’s download site, so note that as of today the file’s name is msicuu2.exe if you the above link goes dead in the future.
If you don’t want to install the Windows Installer CleanUp Utility, use a program such as Universal Extractor (aka UniExtract) to extract the individual files. Once you extract the files, you’ll notice msizap.exe does not exist, but you will find MsiZapA.exe and MsiZapU.exe.
There are two versions of MSIZAP.EXE: MsiZapA.exe (for use in Windows 95, Windows 98 and Windows ME), and MsiZapU.exe (for use in Windows NT, Windows 2000, Windows XP, and Windows Server 2003). The appropriate executable should be renamed MsiZap.exe.
Current msizap.exe options are as follows:
Usage: msizap T[WA!] {product code}
msizap T[WA!] {msi package}
msizap *[WA!] ALLPRODUCTS
msizap PWSA?!
* = remove all Windows Installer folders and regkeys;
adjust shared DLL counts; stop Windows Installer service
T = remove all info for given product code
P = remove In-Progress key
S = remove Rollback Information
A = for any specified removal, just change ACLs to Admin Full Control
W = for all users (by default, only for the current user)
M = remove a managed patch registration info
G = remove orphaned cached Windows Installer data files (for all users)
? = verbose help
! = force ‘yes’ response to any prompt
For more information on the Windows Installer Cleanup Utility and msizap.exe see KB290301.