Sunday, June 19, 2011
Windows domain controller without Windows...
have to try it...
http://www.vmware.com/appliances/directory/393283
Ubuntu(windows) domain controller...
Thursday, June 9, 2011
Resizing Disks used in a MSCS in VMWare
To take a backup of the VMDK:
Stop the cluster nodes.
Rename the VMDK that needs to be expanded with the command:
vmkfstools -E
Clone the VMDK to a thin volume using the original name with the command:
vmkfstools -I -d thin
Grow the clone with the command:
vmkfstools -X
Inflate the cloned VMDK with the command:
vmkfstools -j
Start the cluster.
Remove the old VMDK from the datastore.
------------
backup the vmdk
1. vmkfstools –E servervm.vmdk servervm_old.vmdk (this renames the vmdk)
2. vmkfstools –i servervm_old.vmdk servervm.vmdk –d thin (clones the renamed vmdk to original name in thin format)
3 vmkfstools –X 200G servervm.vmdk (expand the available size to 200 GB)
4. vmkfstools –j servervm.vmdk (inflates the vmdk in eargerzeroedthick format)
Conclusion: I think its just another way to redo the metadata on the VMDK files so it reads the new resized disk properly...
Wednesday, June 8, 2011
Exchange 2010 - hub Transport not accepting SMTP connections, ForeFront client security enabled
http://technet.microsoft.com/en-us/library/bb332342.aspx
Tuesday, May 17, 2011
SCAN option not available at Right Click with Symantec Endpoint Protection
the Right Click - SCAN option is not available when logged in via RDP session on SEP clients.
May be you already knew that, i didnt...
Also, if there is a centralized exception to the folder you are trying to scan manually,
IT WILL STILL NOT SCAN the folder if it is part of the exceptions.
Cheers
Tuesday, May 10, 2011
Reset password while unlocking SQL
Wednesday, April 27, 2011
How to map a network drive to be used by a service
Step one: Open an elevated cmd.exe prompt (Run as administrator)
Step two: Elevate again to root using PSExec.exe: Navigate to the folder containing SysinternalsSuite and execute the following command "psexec -s cmd.exe" you are now inside of a prompt that is "nt authority\system" and you can prove this by typing "whoami"
Step Three: Create the persistent mapped drive as the SYSTEM account with the following command "net use z: \servername\sharedfolder /persistent:yes"
It's that easy!
WARNING: You can only remove this mapping the same way you created it, from the SYSTEM account. If you need to remove it, follow steps 1 and 2 but change the command on step 3 to: "net use z: /delete"
NOTE: The newly created mapped drive will now appear for ALL users of this system but they will see it displayed as "Disconnected Network Drive (Z:)". Do not let the name fool you. It may claim to be disconnected but it will work for everyone. That's how you can tell this hack is not supported by Microsoft.
UPDATE
Hi all,
Thanks for the feedback.
I have finally had a chance to try and find a workaround to get the mapping done when the computer restarts. I have done limited testing, but so far this seems to have worked.
Follow this article to create a service with whatever name u like
http://support.microsoft.com/kb/137890
I suggest creating something like
C:\Program Files\Resource Kit\Instsrv.exe MapDriveAsSystem C:\Program Files\Resource Kit\Srvany.exe
Then do the regedit as described in the article.
There is a bit more to it then just running the psexec command.
You HAVE TO MAKE SURE THE SERVICE RUNS under a USER account and NOT LOCAL SYSTEM
Then its upto you to set the service startup requirement. The service stays in started state although the psexec has completed its task. So if you were to manually delete the mapping the service would show as started regardless. To improvise on that. may be you could create a bat file with the psexec command to map as system and then a SC command to stop the same service.
Shouldnt matter though, as we are only doing this service creation to handle the mapping on a computer reboot.
Hope it helps.
Cheers
Rahul
Monday, March 28, 2011
ICA Connections Hangs or Stops at 'Connection Established, Negotiating Capabilities'
ICA Connections Hangs or Stops at 'Connection Established, Negotiating Capabilities'
Symptoms
ICA connections hang or stop at "Connection established. Negotiating capabilities” specific to client workstation or domain user . Also connecting to a specific server always hang at “Connection Established, Negotiating Capabilities”.
My machine + his\her credentials = success
Another machine + his\her credentials = success
His\Her home machine + his\her credentials = failure
His\Her home machine + test ID = failure
Cause
Usually this is caused by an inaccessible license server.
Server results in not getting a correct license, probably the license server detects that several servers are using the same license and blocks it, especially if servers are cloned.
Resolution
Caution! This procedure requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that might require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Back up the registry before you edit it.
1. On client workstations with this issue, change the permissions on the registry key HKLM\SOFTWARE\Microsoft\MSLicensing. Give the Users Group Full Control or specific domain user account.
If you delete the key, Terminal Services recreates it when it acquires a license. However, the permissions on this key are set to read-only by default. Only administrators have full control rights. This means that only an administrator can request a Terminal Services license for this server. Once it is acquired, every user can use it.
2. Delete (rename or export key to be safe) the HKLM\Software\Microsoft\MSLicensing\HardwareID and HKLM\Software\Microsoft\MSLicensing\Store keys
More Information
Other solutions:
For Windows 2000 Professional systems: delete the License000x key to resolve the issue.
On each of your Citrix Presentation servers open the registry editor and navigate to
"HKEY Local Machine/System/Current ControlSet/Services/TermService/Parameters".
Delete the following keys (after making a backup):
Certificate
X509 Certificate
X509 Certificate ID
Reboot your server and verify that the issue is gone.