As of 10-9-11, Citrix’s Kaviza appliance will not run on ESX 5.0. Don’t waste your time. Stick with ESX 4.1
-
Pages
-
Categories
-
Archives
-
RSS Feeds
-
Meta
As of 10-9-11, Citrix’s Kaviza appliance will not run on ESX 5.0. Don’t waste your time. Stick with ESX 4.1
Experience has shown that less-experienced admins have a higher propensity for going “heads down.” Heads down occurs when you are troubleshooting a problem and you either get tunnel vision or lose perspective on time. Tunnel vision is the trap of not considering external factors that might be causing your problem.
Taking on troubleshooting as a personal crusade is nothing more than a waste of time. Six hours later, although you may have resolved a TCP/IP configuration , it probably could have been solved within one or two hours if outside resources had been consulted. You will find no more (painfully) honest statement.
In any case, it is essential to limit your core troubleshooting efforts to just one hour before stepping back from the situation and calling in help and reinforcements.
VPN Remote Access.
Three steps.
1. Tunnel Policy – Network Tunnel
2. Route Routing
3. NAT Exempt
commands:
sh run nat – to view nat config. nat 0 indicates nat exempt
sh run
Rebooting your server with the datastore during the same period as the others cause the other servers to come back online with their logons disabled. Make sure to stagger the reboots if this is the case.
Gain console access and Run this command: CHANGE LOGON /ENABLE.
In the Exchange Management Shell execute..
eseutil /mh <path/databasefilename>
In the output concentrate on the Status Field and “Log Required” Field. If status is in a “Dirty Shutdown” state note the “Log Required” value. Navigate to the log file directory, sort by date modified and then move all log files after the the log file name noted in the “Log Required” Field.
These are the basic steps:
To commands Monitor/Troubleshoot QOS issues:
show policy-maps int Fastethernet x
Show access-list ACLname
** be concerend with packet that are being dropped from the packet. usually indicates that priority level is not set high enough. Don’t be too concerend with packets that are being dropped from the default policy. Computer transfer communication are more forgiving that voice.
Cisco’s implemenation of Quality of Service Policies with DSCP http://www.cisco.com/en/US/tech/tk543/tk757/technologies_tech_note09186a00800949f2.shtml
Fix Active Directory DNS issues.
Use the Windows Support Tool and run these command:
dcdiag /fix
netdiag /fix
ipconfig /flushdns
ipcofnig /registerdns
net stop server
net start server
Reboot server. If this is not an option, go into Services and start any automatic services that are stopped.
*** If the Active Directory DNS records do not appear, you may need to manually re-create the DNS zone.
The steps are…
1. Install Drive
2. Use ACU to EXPAND the Array
3. Use ACU to EXTEND your logical drive(s)
4. Use DISKPART for your D: drive
5. Use 3rd party for your C: Drive or use 3RD PARTY for both drives. (Diskpart does not work on system drives- only data drives)
How to extend a data volume in Windows Server 2003, in Windows XP, in Windows 2000, and in Windows Server 2008
Is not on DVD. Is installed automatically in c:\Windows\System32\Sysprep\sysprep.exe

Choose ‘Generalize’ to create new SID.
Use vmkfstools to clone vmdk disk. (faster, allocates full space thus reducing fragmentation)
Use cp command to copy files.
Example:
esxhost1<root>: vmkfstools -i /vmfs/volumes/datastoreold/vmfolderold/vmold.vmdk /vmfs/volumes/datastoreNEW/vmfolderNEW/vmNEW.vmdk
(make sure you include the new vmdk file name or you will get an error ‘file already exist’)
Highly recommended that you power-down the vm first. Otherwise do a snapshot before the clone to create deltas.
Copy .vmdk files only using vmkfstools (no -flat files)
Then cp *.vmx files.
remove and readd VM from inventory.