Kevin Oppihle's Tech Notes

Problem: At some point Kaviza or VDI in a Box did not remove deactivated computers from AD either due to an improper shutdown, timing issue,… finding out which are in use and are not can take some time. Here is how I sped up the cleanup process. Solution: Follow the steps below to export your computer names to bat log file. Then edit the bat file to ping the systems and export to a log file then review the results and clean up ad. All of my Kaviza systems have the same prefix of FBWKVFB-x so I ran the following command to pull the list from AD and export to a bat file: Dsquery computer domainroot –name FBWKVFB-* > c:\kavizapc.bat then edit the bat file and use the find and replace command to replace the excess fields. Here is an example of the unedited output: "CN=FBWKVFB-7C246DT,OU=SBComputers,OU=Computers,OU=MyBusiness,DC=ad,DC=domain" Find “CN= Replace with Ping –4                                    Note : the “-4” command is to use IPV4 ping only if you want to p

Problem: You need to change your network interface/Switch on a VM from the Command line interface on your Server 2012 Hyper-V free console Solution: Use the following powershell commands: Note: you do not need to download or install any third party Powershell add-ons to perform these tasks. In the Administrative window type in “Powershell.exe” and enter Now List your VM’s by typing “Get-VM” Now we will check its current “switch” by typing in “Get-VMNetworkAdapter” which will then prompt you for the VMname or names you wish to query Now we will change its current “switch” to my switch named “HV VM TRAFFIC”  by typing in “Connect-VMNetworkAdapter –Switchname “HV VM TRAFFIC” which will then prompt you for the VMname or names you wish to change to this switch Now we will check its current “switch” by typing in “Get-VMNetworkAdapter” which will then prompt you for the VMname or names you wish to query As you can see above the SwitchName is now “HV VM TRAFFIC”

Problem: You need to shutdown restart or start a VM from the Command line interface on your Server 2012 Hyper-V free console Solution: Use the following powershell commands: Note: you do not need to download or install any third party Powershell add-ons to perform these tasks. In the Administrative window type in “Powershell.exe” and enter Now List your VM’s by typing “Get-VM” You can see x-UMVM1 is off to turn it on type in “Start-VM “VMname”” To check the status you can either type in “Get-VM” and see all VM’s or you can type in “Get-VM “VMname”” to see just the VM you are working on: To shutdown your VM cleanly type in “Stop-VM “VMname”” Again to check the status you can either type in “Get-VM” and see all VM’s or you can type in “Get-VM “VMname”” to see just the VM you are working on: To do a HARD restart of you VM type in “restart-VM “VMName”” Note: I would recommend you do a Stop and start instead if possible

Problem: You are changing from DSL or other internet service to use Uverse for your business. You need to have an external facing IP address for email, website, remote access or other traffic. Solution : First you should have an external facing firewall.  Second when you purchase your Uverse account make sure you specify that you need external Static IP addresses. Third follow the steps below: Once the ATT installation technician relays to you your IP information including your usable addresses, Modem IP, subnet mask, and DNS information. Setup your externally facing firewall with one of the usable addresses using the new schema settings. Once your external firewall is ready log onto the ATT Uverse Modem Note: you will need the Access Code located on the label of the modem Once on the router select “Firewall” >“IP Passthrough” Select “Default Server” and enter in the IP address of your externally facing firewall and “Save” as shown below: You will then be prompted to restart the

Problem: Either you set chkdsk to run at next restart or Windows did due to a problem with the drive. Initially the check disk pauses at 0%-2% for a minute or two then it jumps up to 28% and appears to stop or hang. You see no change in 15-30 minutes. Solution: WAIT! The older chkdsk program does not show an accurate percentage of the process as it runs. It will tend to stop at 28% for a long time, even well over an hour or more, depending on the data, drive, and your need for it to finish quicker. Just about the time you are ready to give up it will jump to Completed. 

Problem: You upgraded or installed Quickbooks 2014 you registered online and it hangs the first time you try to logon to your data file at local registration. Solution: Skip the local registration initially, Open the data file and convert as necessary if upgrading. Once you are in the data file then initiate the registration after using the tab in the top right corner. In my instance it appeared to get confused and lock up when trying to perform both tasks.