The below gives you the instruction to download and install the pack on Windows 7
Remote Server Administration Tools for Windows 7
Tuesday, April 6, 2010
Windows 7 : Remote Server Administration Tools
To install the Various Admin Tools just like 2000/2003 Admin Packs, Windows 7 has its own pack call the RSAT (Remote Server Administration Tools)
The below gives you the instruction to download and install the pack on Windows 7
Remote Server Administration Tools for Windows 7
The below gives you the instruction to download and install the pack on Windows 7
Remote Server Administration Tools for Windows 7
Monday, April 5, 2010
Windows XP : Unable to find Security Tab.
Open Windows Explorer, go to Tools, Folder Options, View and uncheck Use Simple File Sharing.
Windows XP : Security enhancement for Internet kiosk
The followings are the settings down on the EMC Internet Kiosk PC.
1. GPEDIT.MSC
2. User Configuration > Administrative Templates > Start Menu and Taskbar
a. Remove Programs on Settings Menu.
b. Remove Network Connections from Start Menu.
c. Remove Search menu from Start Menu.
d. Remove Run menu from Start Menu.
e. Remove My Pictures icon from Start Menu.
f. Remove My Music icon from Start Menu.
g. Remove My Network Places icon from Start Menu.
h. Remove Drag-and-drop context menus on the Start Menu.
i. Prevent changes to Taskbar and Start Menu Settings.
j. Remove access to the context menus for the taskbar.
k. Turn off user tracking.
l. Remove frequent programs list from the Start Menu.
m. Remove Set Program Access and Defaults from Start Menu.
3. User Configuration > Administrative Templates > Control Panel
a. Prohibit access to the Control Panel.
4. Remove Everyone's permission on these 2 files:
a. %SystemRoot%\Inf\Usbstor.pnf
b. %SystemRoot%\Inf\Usbstor.inf
5. Regedit, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\UsbStor, Change "Start" value to 4 Hexadecimal.
Related Links:
How can I prevent users from connecting to a USB storage device?
How to disable USB sticks and limit access to USB storage devices on Windows systems
Wednesday, March 10, 2010
VMware client on Windows 7 : The type initializer for "VirtualInfrastrcture.Utils.HttpWebRequestProxy" threw an exception
Vmware client is not fully tested on Windows 7 yet. So if you are running the client from windows 7, installation of the client will not give you any error, only when connecting to the host you will encounter the below scenario:
Error Parsing the server "192.168.1.10" "clients.xml" file Login will continue contact your system administrator
And after clicking "OK"
The type initializer for "VirtualInfrastrcture.Utils.HttpWebRequestProxy" threw an exception
To do a bypass to the above problem, try this:
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a element and a element as shown below. Save the file.
4. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
5. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.
Related discussion: vsphere client on Windows 7 rc
Error Parsing the server "192.168.1.10" "clients.xml" file Login will continue contact your system administrator
And after clicking "OK"
The type initializer for "VirtualInfrastrcture.Utils.HttpWebRequestProxy" threw an exception
To do a bypass to the above problem, try this:
1. Obtain a copy of %SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dll from a non Windows 7 machine that has .NET 3.5 SP1 installed.
2. Create a folder in the Windows 7 machine where the vSphere client is installed and copy the file from step 1 into this folder. For example, create the folder under the vSphere client launcher installation directory (+%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib).
3. In the vSphere client launcher directory, open the VpxClient.exe.config file in a text editor and add a
4. Create a batch file (e.g. *VpxClient.cmd*) in a suitable location. In this file add a command to set the DEVPATH environment variable to the folder where you copied the System.dll assembly in step 2 and a second command to launch the vSphere client. Save the file. For example,
SET DEVPATH=%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib
"%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe"
5. (Optional) Replace the shortcut on the start menu to point to the batch file created in the previous step. Change the shortcut properties to run minimized so that the command window is not shown.
You can now use the VpxClient.cmd (or the shortcut) to launch the vSphere client in Windows 7.
Note that this workaround bypasses the normal .NET Framework loading mechanism so that assembly versions in the DEVPATH folder are no longer checked. Handle with care.
Related discussion: vsphere client on Windows 7 rc
Sunday, March 7, 2010
The following GPOs were not applied because they were filtered out : denied security
Found this error when checking on gpresult of a workstation:
Found that WallPaper/ScreenSaver is not applied due to Filtering: Denied (Security)
(Filtering: Not Applied (Empty) is because the policy is empty OR the policy does not have settings for this workstation/user)
The error Filtering: Denied (Security) is mainly caused by the security filtering on the GPO.
Check on Group Policy management console and found that the security filtering is empty. Added the authenticated users into the list and the problem is solved.
Found that WallPaper/ScreenSaver is not applied due to Filtering: Denied (Security)
(Filtering: Not Applied (Empty) is because the policy is empty OR the policy does not have settings for this workstation/user)
The error Filtering: Denied (Security) is mainly caused by the security filtering on the GPO.
Check on Group Policy management console and found that the security filtering is empty. Added the authenticated users into the list and the problem is solved.
Wednesday, March 3, 2010
Exchange 2003 : Message tracking not working
The first day I joined AO, I found this problem on their one and only exchange server.
Server info
============
Exchange 2003 SP2.
Tried to use message tracking center but it generates the error:
" the search could not be completed. Check to see that the Microsoft Exchange Management service is running on all Exchange 2000 and Exchange 2003 installations."
Verified that
1. WMI service is running
2. Exchange managment is running
3. Exchange services running using Local system account
4. Under exchange services > properties > log on > interact with desktop is unchecked.
Looking at the message track log path (Log File Directory text field), it contains the below error:
"An error occurred during a call to Windows Management Instrumentation
ID no: 80041013
Exchange System Manager"
==================================
The message tracking log path becomes normal for a while after reboot, but it will later return the error again.
Discussion on technet suggested that this is a problem with WMI. Hence re-registering the DLLs is the way to go:
mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\wbemcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\smtpcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\msgtrk.mof"
Restart the Microsoft Exchange management service and WMI service.
After registering the DLLs and restarting the server. The message tracking is back to normal.
=========================================
NO IT DOES NOT WORK!
after a few days. the error will come up again. and message tracking will fail again.
Suspecting that when doing a message tracking search, something trigger the error to occur.
Related links:
Technet Discussion
Server info
============
Exchange 2003 SP2.
Tried to use message tracking center but it generates the error:
" the search could not be completed. Check to see that the Microsoft Exchange Management service is running on all Exchange 2000 and Exchange 2003 installations."
Verified that
1. WMI service is running
2. Exchange managment is running
3. Exchange services running using Local system account
4. Under exchange services > properties > log on > interact with desktop is unchecked.
Looking at the message track log path (Log File Directory text field), it contains the below error:
"An error occurred during a call to Windows Management Instrumentation
ID no: 80041013
Exchange System Manager"
==================================
The message tracking log path becomes normal for a while after reboot, but it will later return the error again.
Discussion on technet suggested that this is a problem with WMI. Hence re-registering the DLLs is the way to go:
mofcomp.exe -class:forceupdate C:\WINDOWS\system32\WBEM\exmgmt.mof
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\wbemcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\smtpcons.mof"
mofcomp.exe -n:root\cimv2\applications\exchange "c:\winnt\system32\wbem\msgtrk.mof"
Restart the Microsoft Exchange management service and WMI service.
After registering the DLLs and restarting the server. The message tracking is back to normal.
=========================================
NO IT DOES NOT WORK!
after a few days. the error will come up again. and message tracking will fail again.
Suspecting that when doing a message tracking search, something trigger the error to occur.
Related links:
Technet Discussion
Wednesday, February 10, 2010
Windows 2008 File Server Resource Manager
As part of the file services for Windows Server 2008, File Server Resource Manager provides a concise, user-friendly and functional console for administrator to govern their file server.
As seen here, the FSRM consists a few functions
1. Quota Management
To easily control users' storage quota. Quota is assigned to folders (not users), hence I guess you cannot define different quota for individuals within the same folder. Probably will need to do it the 2003 way, Disk managment > Drive properties > quota.
A good thing here is you can set notification to be sent when a certain threshold is met.
2. File Screening Management
This tool allows you to do file filtering for your file servers. You might want to control users from storing media files on the file server, this tool provides an easy way to do that.
and this tool goes by folder location as well, so we are not able to set individual screening here.
When the file type is being screened, users will receive an alert when they want to store the file, a notification can be set to send to a particular admin (it's good to set it to folder owners for their own discretion)
3. Storage Report Management
Storage Report Management allows you to generate reports for your file server.
4. Classification Management
This allows you to set a certain properties and rules on your files, for advance file management I guess. Not quite sure how to use this yet.
5. File Management Task
This allows you to generate a certain task when condition is met, and can be combined with Classification Management. Not quite sure how to use this yet.
Related Link:
File Server Resource Manager Step-by-Step Guide for Windows Server 2008
As seen here, the FSRM consists a few functions
1. Quota Management
To easily control users' storage quota. Quota is assigned to folders (not users), hence I guess you cannot define different quota for individuals within the same folder. Probably will need to do it the 2003 way, Disk managment > Drive properties > quota.
A good thing here is you can set notification to be sent when a certain threshold is met.
2. File Screening Management
This tool allows you to do file filtering for your file servers. You might want to control users from storing media files on the file server, this tool provides an easy way to do that.
and this tool goes by folder location as well, so we are not able to set individual screening here.
When the file type is being screened, users will receive an alert when they want to store the file, a notification can be set to send to a particular admin (it's good to set it to folder owners for their own discretion)
3. Storage Report Management
Storage Report Management allows you to generate reports for your file server.
4. Classification Management
This allows you to set a certain properties and rules on your files, for advance file management I guess. Not quite sure how to use this yet.
5. File Management Task
This allows you to generate a certain task when condition is met, and can be combined with Classification Management. Not quite sure how to use this yet.
Related Link:
File Server Resource Manager Step-by-Step Guide for Windows Server 2008
Subscribe to:
Posts (Atom)