Friday, December 28, 2012

Steps if account gets frequently lockout


Try this steps if account gets frequently lockout.



1) remove passwords by clicking on Start => Run => type "rundll32.exe

keymgr.dll, KRShowKeyMgr" and then delete the Domain-related passords;

2) remove passwords in Internet Explorer => Tools => Internet Options =>

Content => Personal Information => Auto Complete => Clear Passwords;

3) Delete cookies in Internet Explorer => Tools => Internet Options =>

General;

4) Disconnect (note the path before disconnecting) all networks drives,

reboot, then map them again;



More often than not it is an explicite drive mapping

You can also take help from Microsoft Acount LockOut tool, Which can be downloaded from the Microsoft website
And run eventcomMT.exe file to check event ids - for this please refer KB824209



Sunday, December 16, 2012

All Citrix Related Issues

For Citrix related issues you can always get the help from their support web site

I've tried this and it really works, It also helps you to find tools required to perform any troubleshooting step
Like XDPING


http://support.citrix.com/

To create a desktop group - Citrix

Before creating a desktop group, understand the different machine types available to you, and note the following:




You can only create a desktop group if at least one machine remains unused in the catalog you select

You cannot use a machine in more than one desktop group

You can create desktop groups from multiple catalogs with the same machine type

You cannot create mixed desktop groups from catalogs with multiple machine types



In Desktop Studio, select the Assignments node in the left pane and click Create desktop group.

On the Catalog page, select a catalog for this desktop group, and enter the number of machines the group will consume from the catalog.

Tip: If machine administrators include the total number of machines in a catalog's description, this appears on the Catalog page. Assignment administrators can use the number in conjunction with their selections in the wizard to ensure sufficient machines are available for the desktop group.

On the Users page, add the users or user groups that can access the desktops, and enter the number of desktops available to each user. You can select user groups by browsing or entering a list of Active Directory users and groups each separated by a semicolon. For private desktop groups, you can import user data from a file after you create the group.



This page is displayed only if the group is based on pooled - static, existing, or physical machines and they have not already been allocated accounts.

On the Machine allocation page, confirm the mapping of machines to users for any machines that were allocated when the catalog was created.

On the Delegation page, select the XenDesktop administrators who will manage this desktop group. All XenDesktop administrators, including help desk administrators, are displayed.

On the Summary page, check all details, and enter a name that users see and a name that administrators see.

To find desktops, sessions, and desktop groups - Citrix

In Desktop Studio, click the Search node.


Enter the name or part of the name of the desktop you want to find.

Optionally, save your search for later use.



Alternatively, use the unfold button to perform an advanced search by building an expression from the available desktop, session, desktop group, or catalog properties.

Use the following tips to speed up your search:



To locate a user device connected to a virtual desktop, use Endpoint and Is, and enter the device's name, or use Endpoint (IP) and Is, and enter the device's IP address.

To locate active sessions, use Session State, Is, and Connected

To list all of the machines in a desktop group, select the group (from the Search or Assignments node) and click View machines

To display other details in search results, right-click a column heading and select Select columns



To enable or disable maintenance mode

XenDesktop regains control over the desktops when you take them out of maintenance mode.




In Desktop Studio, do one of the following:

To locate individual desktops, use Search, or select a desktop group and click View machines

To locate a desktop group, select the Assignments node

Select the desktop or desktop group and click Enable maintenance mode or Disable maintenance mode.

Expand an RDM LUN of a VMware VM

Ensure that there are no snapshots on the disk before attempting this operation. If there are snapshots present, commit them. Otherwise, you may experience data corruption Steps to expand RDM in Physical Compatibility Mode In the vSphere client, select the VM which you want to extend the disk, Edit Settings and check the disk whether it’s a Physical or virtual compatibility mode. 1. If it’s a physical compatibility mode, Good news is no need to do anything from the VM side. No down time required of VM 2. Expand the RDM LUN from the SAN Side – Performed by Storage team 3. Re-Scan the HBA’s at ESX host ( Configuration Tab -> Storage Adapters -> Rescan on top right) and see the new LUN Size is observed 4. Now go to the VM and open Disk Management, you should see extra space available as Unallocated, if not means it’s not expanded properly or require rescan of HBA adapters 5. Open disk part / Ext part utility and extend the available space. Steps to expand RDM in Virtual Compatibility Mode 1. Shutdown the VM and remove the RDM from the virtual machine. Before removing, make note of SCSIX: Y position from VM settings. 2. Expand the RDM LUN from the SAN Side – Performed by Storage team 3. Re-Scan on the ESX and verity the new LUN size is expanded. 4. Recreate the RDM Mapping. Go to VM -> Edit Settings -> Add Hard Disk -> select RDM, then select the same position we noted above for SCSI 5. Start the VM and check in Disk Management 6. Use disk part utility to extend the added space Testing & Confirmation In My Computer, confirm that the desired drive is expanded.

Disk Space Issues

C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\* C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\Downloads\* C:\Documents and Settings\All Users\Application Data\Symantec\Cached Installs (http://www.symantec.com/business/support/index?page=content&id=TECH106042&locale=en_US) C:\Documents and Settings\All Users\Application Data\GFI\LANguard 10\PatchManagement\* C:\Documents and Settings\All Users\Application Data\VMware\Installer C:\WINDOWS\Installer\$PatchCache$ c:\WINDOWS\ie8updates c:\WINDOWS\ie7updates C:\Windows\SoftwareDistribution\Download\* C:\WINDOWS\ServicePackFiles\i386\* C:\WINDOWS\$NtServicePackUninstall$ C:\Program Files\Altiris\Altiris Agent\Software Delivery c:\Program Files (x86)\Altiris\Altiris Agent\Agents\SoftwareManagement\Software\Delivery\{#} C:\Program Files\Common Files\Symantec Shared\Virusdefs\* C:\Program Files (x86)\Common Files\Symantec Shared\VirusDefs\(old YYYYMMDD.XXX's) C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\content" delete numbered folders {1CD85198-26C6-4bac-8C72-5D34B025DE35} C:\Program Files\Program Files\Common Files\Symantec Shared\SymcData\sesmvirdef32" and delete all dated folders (Example: 20071231.002) C:\Program Files\Program Files\Common Files\Symantec Shared\SymcData\sesmvirdef64" and delete all dated folders (Example: 20071231.002) C:\Program Files\Common Files\Symantec Shared\SymcData\ and delete the following folders: \sesmipsdef32 \sesmipsdef64 \sesmvirdef32 \sesmvirdef64 Also - Empty the Recycle Bin once your file deletion has completed.

Passwordless login on Windows through WinSSHD

1. Log into server 2. Launch WinSSHD Control Panel (you can find this by clicking START and using search) 3. Under Settings click Open Easy Settings 4. Go to Tab #3 Virtual accounts 5. Click Add 6. Under Virtual Account Name enter the Unix Name 7. Click Public Keys 8. On new window that opens, click Import 9. Browse to SSH key click OK 10. Click Close to close out the Public Keys window 11. Uncheck “Allow Terminal” 12. To the right of Virtual Filesystem Layout select Limit to root directory 13. A new field will appear “Root Directory” enter the path provided by client. 14. Click OK to close out Account Add window 15. Click Save Changes to close out Easy Settings window.

Replication Test

@echo off echo %date% %time% >>c:\replication.%computername%.log Echo Compiling Replication Summary... REPADMIN /REPLSUMMARY >>c:\replication.%computername%.log Echo Checking DNS... DCDIAG /test:DNS /e /v >>c:\replication.%computername%.log Echo Finished

Thursday, February 16, 2012

Virtual Machine Upgrade Process

Please note that this process will require some downtime.

1. Record the current IP configuration of the guest operating system. You’ll end up needing to recreate it.

2. Upgrade VMware Tools in the guest operating system. You can do this by right-clicking on the virtual machine and selecting Guest > Install/Upgrade VMware Tools. When prompted, choose to perform an automatic tools upgrade. When the VMware Tools upgrade is complete, the virtual machine will reboot.

3. After the guest operating system reboots and is back up again, shutdown the guest operating system. You can do this by right-clicking on the virtual machine and selecting Power > Shutdown Guest.

4. Upgrade the virtual machine hardware by right-clicking the virtual machine and selecting Upgrade Virtual Hardware.

5. In the virtual machine properties, add a new network adapter of the type VMXNET3 and attach it to the same port group/dvPort group as the first network adapter.

6. Remove the first/original network adapter.

7. Add a new virtual hard disk to the virtual machine. Be sure to attach it to SCSI node 1:x; this will add a second SCSI adapter to the virtual machine. The size of the virtual hard disk is irrelevant.

8. Change the type of the newly-added second SCSI adapter to VMware Paravirtual.

9. Click OK to commit the changes you’ve made to the virtual machine.

10. Power on the virtual machine. When the guest operating system is fully booted, log in and recreate the network configuration you recorded for the guest back in step 1. Windows may report an error that the network configuration is already used by a different adapter, but proceed anyway. Once you’ve finished, shut down the guest operating system again.

11. Edit the virtual machine to remove the second hard disk you just added.

12. While still in the virtual machine properties, change the type of the original SCSI controller to VMware Paravirtual (NOTE: See update below.)

13. Power on the virtual machine. When the guest operating system is fully booted up, log in.

14. Create a new system environment variable named DEVMGR_SHOW_NONPRESENT_DEVICES and set the value to 1.

15. Launch Device Manager and from the View menu select Show Hidden Devices.

16. Remove the drivers for the old network adapter and old SCSI adapter. Close Device Manager and you’re done!

If you perform these steps on a template, then you can be assured that all future virtual machines cloned from this template also have the latest Para virtualized drivers installed for maximum performance.
UPDATE: Per this VMware KB article, VMware doesn’t support using the PVSCSI adapter for boot devices. That is not to say that it doesn’t work (it does work), but that it is not supported. Thanks to Eddy for pointing that out in the comments!


Some issues you might encounter after up gradation:-
• Disks on windows 2008 will go offline after the upgrade. This is highlighted in VMware Knowledge Base article 1013109: “Upgrading virtual hardware in ESX 4 may cause Windows 2008 disks to go offline“. The problems described in the article are unique to Windows 2008 Enterprise and Datacenter editions only.
• Windows 2003 NLB cluster nodes will be destroyed (offline). I found out myself that the upgrade script cannot reconfigure the nlb cluster nodes. You have to connect to the node which is not upgraded and re add the node.
• The hardware upgrade will reboot the server once; many applications need an extra reboot to function correctly. This is because windows will discover the new hardware. For the rest i couldn’t get the answer why it needed an extra reboot.

How to Add a Hard Disk to a Virtual Machine in VMware ESX Server

When you add a hard disk to a virtual machine, you can create a new virtual disk, add an existing virtual disk, or add a mapped SAN LUN.

Procedure:
1. Start the Add Hardware wizard.

2. Select Hard Disk, and click Next.

3. Select the type of storage for the virtual machine’s disk, and click Next. You can store virtual machine data in a new virtual disk, an existing virtual disk, or a Mapped SAN LUN. A virtual disk, which appears as a single hard disk to the guest operating system, is composed of one or more files on the host file system. Virtual disks can easily be copied or moved on the same host or between hosts.

4. If you selected Create a new virtual disk, do the following:
a. Enter the disk capacity.
b. Select the location as either Store with the virtual machine or Specify a datastore.
c. If you selected Specify a datastore, browse for the datastore location, and click Next. Continue with Step 7.

5. If you selected an existing disk, browse for the disk file path and click Next

6. If you selected Mapped SAN LUN:
a. Select the LUN that you want to use for the raw disk, and click Next.
b. Select a datastore and click Next.
c. Select the compatibility mode: physical to allow the guest operating system to access the hardware directly or virtual to allow the virtual machine to use VMware snapshots and other advanced functions. Click Next.

7. Specify the virtual device node.

8. Set virtual disk mode options:
a. Select Independent to make the disk independent. Independent disks are not affected by snapshots.
b. If you selected Independent, select one of the two modes for independent disks:
 Persistent – The disk operates normally except that changes to the disk are permanent even if the virtual machine is reverted to a snapshot.
 Nonpersistent – The disk appears to operate normally, but whenever the virtual machine is powered off or reverted to a snapshot, the contents of the disk return to their original state. All later changes are discarded.

9. Click Next.

10. Review the information, and click Finish.

Domain Account gets frequently lockout

1) Remove passwords by clicking on Start => Run => type "rundll32.exe
keymgr.dll, KRShowKeyMgr" and then delete the Domain-related passords;

2) Remove passwords in Internet Explorer => Tools => Internet Options =>
Content => Personal Information => Auto Complete => Clear Passwords;

3) Delete cookies in Internet Explorer => Tools => Internet Options =>
General;

4) Disconnect (note the path before disconnecting) all networks drives,
reboot, then map them again;

Domain Account gets frequently lockout


1) Remove passwords by clicking on Start => Run => type "rundll32.exe
keymgr.dll, KRShowKeyMgr" and then delete the Domain-related passords;

2) Remove passwords in Internet Explorer => Tools => Internet Options =>
Content => Personal Information => Auto Complete => Clear Passwords;

3) Delete cookies in Internet Explorer => Tools => Internet Options =>
General;

4) Disconnect (note the path before disconnecting) all networks drives,
reboot, then map them again;