vGeek

Compare Different Laptops for Home Lab

noreply@blogger.com (kunal) — Mon, 9 Jul 2018 14:48:00 +0530

Compare Different Laptops

As we all know, there are many types of laptop computers that were manufactured to suit every need and requirement. This is why in what follows we will compare different laptop computers to get at least an idea about what you should look for when you want to buy a laptop.

There are 5 big types of laptop computers: desktop replacements, ultraportable laptops, standard laptops, thin and light laptops and tablet PCs. As to compare different laptop computers, we will discuss a bit about the things you’ll get and the things you’ll miss when and if you buy a laptop from the categories above mentioned.

If you decide upon a desktop replacement - that is a laptop that has all the things your former computer had, but in a more stylish practical chassis - than you’ll get a widescreen with a sharp display and great colours, a i5 processor, enough memory and sophisticated style. Such a laptop will also come with a numeric pad, a thing that is really rare on laptop computers nowadays.

Such a laptop is good for gaming, for editing and also for a good sound, as most of them with an integrated subwoofer. Though you get all these things, there are also some downsides of a desktop replacement laptop. It is not portable, as it weighs a lot due to all its components, their battery life is really poor and they are, by far, the most expensive (from $1500 to $4000).

While the desktop replacements are so hard to carry around, the ultraportable laptops are the ones you should think of if you are a traveler. Such a laptop is very compact and has a great design, but the performance is really low. If you buy one, you’ll also find that the battery life is also very poor, the screen is small and the keyboard is also very unpractical, as it too is very small.

Also, you won’t get a CD or DVD drive either, because the ultraportable laptops have to be small and really light. Know more about the pros and cons of ultraportable laptops from LaptopJudge and no matter what you choose to buy, check the reviews and ratings carefully before buying.

Standard laptops are really affordable; they provide great performance and excellent battery life. So if you need to travel a lot and also work on your laptop, then such a laptop is a great choice. The only bad parts are that they are not as portable as the ones mentioned above, and they don’t have upgraded graphics chips, so they won’t come close to the frame rates offered by desktop replacements.

Thin and light laptops are by far the best in the traveling domain because they combine power with battery life. They also have great displays and many wireless options, so you can stay connected whenever. However, they lack USB ports, there are only 2 or 3, which to be honest are less than enough and they utilize shared system RAM in the graphics department.

Finally, the tablet PCs will provide mobility, as they are very small; they have 2 viewing modes, either portrait or landscape and they also have a great battery life. However, they lack performance, screen quality, and optical drive, as you won’t get a CD or DVD drive. If you find this post helpful, check out "Best 2-person desk for College Students"

Which laptop do you want to use? And for what? Let me know through comments.

Stellar Data Recovery Technician Review

noreply@blogger.com (kunal) — Wed, 27 Jun 2018 20:24:00 +0530

Stellar Data Recovery Technician is Powerful software utility tool to recover data, it is not only useful for IT environment but also can be used by end users as well, This software is capable of recovering data which is lost or damaged from RAID 0, RAID 5 and RAID 6 drives. It is a complete solution with advanced features to recover files, photos, videos, emails etc. not only from Windows but linux and Mac - based hard drives as well as external media. Along with this software has three additional tools i.e. Stellar Drive Monitor, Stellar Repair for Photo, Stellar Repair for Video. Stellar proposes a comprehensible UI interface, reckless and full scans and a extensive choice of selections. You can't mistake with choosing this solution, however your decision might differ to preview its results.

The Stellar brand stances as one of the most trustworthy IT software provider today, thanks to a wide-ranging of data utilities planned to secure users out of tough conditions. Through this evaluation, I’ll be looking at the business’s data recovery solution, called Data Recovery Expert, which works for both Mac, Linux and Windows OSes.

Stellar Data Recovery can be used to revive files that you, an application, your OS or a virus have deleted. It can also be castoff to recuperate information from not working or corrupted hard drives, or erased, RAW or non-mounting partitions.

Bonuses that we like comprise the ability to recover data from external HDD, flash USB drives and damaged CDs or DVDs. The tool also provisions duplicating, which can be used to reproduction your whole file system or a volume onto a new hdd in case yours is deteriorating.

Stellar works proficiently and has one of the most feature-rich options of any data retrieval tool I verified, with options to scan by file type, scan specific folders and preview files while your scan is still in progress.

I was very enthralled with Stellar after hitting it through our difficult government that I called it my highest recommended data recovery tool for PC. Read on to find out the full scope of its capabilities, plus where it falls a little short.

Features

Here’s a brief impression of the main features of Stellar Data Recovery Technician. We highlighted this software bundle because it proposals RAW partition recovery, a significant feature for any data recovery software.

Both of these are comprised in the additional exclusive “technician” edition of Stellar Data Recovery. A startup disk lets you recuperate data information from a computer that won’t boot due to a corrupted boot partition.

Stellar provisions recovery of most file types. The list includes:

Documents: Powerpoint, PDF, Word, Excel,
Images: RAW, Photoshop, Illustrator, JPEG, PNG,
Audio: AIFF, AAC, Ogg, MP3, WAV,
Videos: AVI, WMV, MPEG-4, QuickTime,
Archives: RAR, Stuffit, Zip, Gzip,

Also, you can add other file formats from the Setting option of the software

In the occasional occurrence that a file kind isn’t maintained, the software permits you describe new file categories if you have five examples that it can use to study from.

Stellar also take cares the common file systems used by Windows and Windows, Mac and Linux with Stellar Toolkit for Data Recovery

Windows: NTFS, FAT16, FAT32, exFAT
Mac: HFS, HFS+
Removable Storage: ExFat
Linux: Ext2, Ext3, and Ext4

Installation Process

Installation Procedure for Stellar is very simple, I have downloaded trial version from https://www.stellarinfo.com/windows-raid-recovery.php. Installation exe is very small in size, just 34 MB, While installation of Stellar Data Recovery Technician on the first page select setup language, by default it is English, click Ok. Next it welcome to the setup wizard, click next, Accept License agreement of Stellar.

Keep all the default unless you want to change Select Destination Location, Start menu folder and addition tasks creating desktop icon.

On ready to Install page review your installation setup settings, and start Installation by clicking Install. Once Completed installation of software, Launch the software by finishing wizard.

Recovery Process

Throughout this sector, I expression at the rudimentary recovery procedure for Stellar Data Recovery. The steps I cover represent the two of the most common procedures users will run with Stellar. We won’t inspect some of the extra procedures, like in what way to add new file kinds or how-to replica a partition in this space.

Once you’ve installed and started Data Recovery Technician, the wizard first asks you to pick the category of file you need to scan for. Being able to choose a definite file kind is a nice inclusion since it decreases scan time.

As it can be seen in the screenshot, Process is very simple to recover data. Click recover data, Here I have multiple options repair video, photo and monitor drive.

On the next page You can select what to recover, I am selecting everything to check the performance, I liked the options it has options separately for documents, emails and multimedia files.

Select the location which you want to scan for recovery, I am again amazed that it has option for common locations, drives and location like raw drive, disk images and raid recovery. I selected C drive - connected drive.

Pressing Scan will start looking for files and folders. Scan is pretty fast.

I re-run the scan with preview option enabled, which shows all the folder it scanned.

In the Preview I see and verify the content of data before recovering.

To recover choose the destination and start saving.

RAID Recovery: Recovers lost or deleted data from RAID 0, RAID 5 and RAID 6 drives, More information provided in next paragraph.
Drive Monitor: It is a add-on SMART utility to monitor Drive health. Disk Monitor integrates a slew of options committed to advisory you in time about the probable disk catastrophes that could wipe away your years’ worth of valuable data. The competent tool provisions constant disk I/O error monitoring, temperature measurements, and SMART status.
Photo Repair: Repair multiple corrupt photos in one go. Supports png, JPEG, bmp, gif & other formats on Windows & Mac. If your images look blurred, grainy, distorted, pix-elated, split. Stellar Mends Photo and will help you revive your valued reminiscences making them high-pitched and rich.
Video Repair: Patch-up several corrupt videos in one go. Supports mp4, mov, avi & other formats, It maintenances the videos that became corrupt while shoot, when executing file transfer, also when editing, converting or processing.

There is good option to try recovering RAID 0, I use a lot RAID 0 for dev and test environment to utilize complete disks. It is the primary level of Redundant array inexpensive disk technology that uses block-level striping without parity or mirroring and has no (or zero) redundancy. RAID 0 progresses performance and storage but has no fault tolerance. Slightly drive catastrophe will cause complete data information loss and the probabilities of failure rises with an surge in the quantity of hard disks.

Raid 5 and Raid 6 are another level of RAID technology which uses Parity (Raid 6 uses double parity) and dispersed data between disks. Raid 5 requires minimum three disks and supports only 1 disk failure. In Raid 6 it is required minimum 4 disks and can support up to 2 disk failure. Recovery process one of the Raid level 5 same looks like below screenshots (Image source www.stellarinfo.com).

There are good options under advanced settings, and they are self explanatory.

Last Judgement

Ended the path of rereading closely 6-7 data recovery solutions, no product overwhelmed me more than Stellar Data Recovery Technician. The product’s data recovery tool is filled with features, very user friendly and runs a snappy, thorough scan.

Anticipation is the best degree to safeguarding you don’t misplace your documents, so be sure and backup your hard drive if you aren’t already. Cheers for reading and please let me know if you have any opinions on Stellar’s RAID recovery and data recovery technician software in the comments below.

Cisco CCNA Lab Guide - Wants to be master of CISCO networks?

noreply@blogger.com (kunal) — Sat, 28 Oct 2017 19:18:00 +0530

How’s it going amigo? I hope you’re keeping well. After long time I am posting on this post and I think it is worth it.

I would like to discuss about http://www.flackbox.com, Author of this website Neil Anderson has been working his socks off on a free Cisco CCNA Lab Guide recently which I think my audience would really love. You can use it to pass the CCNA exam or as a configuration reference for Cisco routers and switches.

There’s a few free guides online but they all cover old out of date exam topics and aren’t great quality, which he guess isn’t surprising when they’re being given away for free. He wanted to produce a guide which is more complete (350+ pages), up to date, better quality and simple to use than all the paid guides out there, but which people can use completely for free. He also have a video course, but the PDF stands alone as a complete lab guide which could really help you further for your careers.

He has attached the guide here so you can have a look. You can download the PDF link at http://www.flackbox.com/cisco-ccna-lab-guide. And it is worth reading.

PART 4.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY

noreply@blogger.com (kunal) — Mon, 3 Oct 2016 17:22:00 +0530

Recently I have started writing on Microsoft Azure blogs, It is to be complete by this week, so do stay tuned on my new website http://vcloud-lab.com.

PART 1 : MICROSOFT AZURE CREATION AND CONFIGURATION OF VPN TUNNEL SERIES
PART 2 : MICROSOFT AZURE CREATING RESOURCE GROUP
PART 3 : MICROSOFT AZURE CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET)
PART 3.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET)
PART 4 : MICROSOFT AZURE CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY VPN
PART 4.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY

New-AzureRmLocalNetworkGateway -Name Poc-VPN_localGateway -ResourceGroupName POC-VPN -Location 'East US 2' -GatewayIpAddress '203.1.1.10' -AddressPrefix @('172.21.101.0/24', '172.21.1.0/24')

Parameters break down as below.
-Name: Name for new local network gateway
-ResourceGroupName: Name of the existing Resource Group in my case is POC-VPN
-Location: This is region where gateway is location, mine is same as existing resource group (East US 2)
-GatewayIPAddress: This is my in-house public internet IP
-AddressPrefix: This is again my inhouse private IPs, I have my servers and desktops in this IP series.

Blog | vGeek - Tales from real IT system Administration environment

noreply@blogger.com (kunal) — Thu, 22 Sep 2016 10:23:00 +0530

Blog | vGeek - Tales from real IT system Administration environment

Top vBlog 2016 - Time to Choose the Top Blogs.

noreply@blogger.com (kunal) — Fri, 6 May 2016 09:54:00 +0530

Last year I registered my blog for top vblog, Again Top vBlog 2016 voting on vSphere-Land has been opened . Please vote me for keep bloggers motivated.

If you appreciate my work and blogs please do vote me. LINK TO VOTE

Below is the paragraph Copying from Eric's post, what should you look for while voting.

Longevity – Anyone can start a blog but it requires dedication, time & effort to keep it going. Some bloggers start a blog only to have it fall to the wayside several months later. Things always come up in life but the good bloggers keep going regardless of what is happening in their life.

Length – It’s easy to make a quick blog post without much content, nothing wrong with this as long as you have good content in the post that people will enjoy. But some bloggers post pretty long detailed posts which takes a lot of time and effort to produce. The tip of the hat goes to these guys that burn the midnight oil trying to get you some great detailed information.

Frequency – Some bloggers post several times a week which provides readers with lots of content. This requires a lot of effort as bloggers have to come up with more content ideas to write about. Frequency ties into length, some do high frequency/low length, some do low frequency/high length, some do both. They’re all good and require a lot of time and effort on the bloggers part.

Quality – It all comes down to whats in the blog post regardless of how often or how long the blog posts are. After reading a blog post if you come away with learning something that you did not previously know and it benefits you in some way then you know you are reading a quality post. Good quality is usually the result of original content, its easy to re-hash something previously published elsewhere, the good bloggers come up with unique content or put their own unique spin on popular topics.

Find CDP or LLDP information on Windows Servers

noreply@blogger.com (kunal) — Fri, 25 Mar 2016 12:12:00 +0530

The Cisco Discovery Protocol (CDP) is a proprietary Data Link Layer protocol developed by Cisco Systems. It is used to share information about other directly connected Cisco equipment, such as the operating system version and IP address.

The Link Layer Discovery Protocol (LLDP) is a vendor-neutral link layer protocol in the Internet Protocol Suite used by network devices for advertising their identity, capabilities, and neighbors on an IEEE 802 local area network, principally wired Ethernet.

From Systems perspective You can view on which Switch and Switchport your Server or desktop NIC/Network cards are connected.

Finding CDP or LLDP information from ESXi very easy as VMware has provisioned separate interface for the same. As in the below screenshot click esxi server, then go to configuration tab, select Networking from Hardware, now as shown click on the CDP button after the Physical Network Card, and you will see CISCO Discovery Protocol, Now you can see I know which switch port I am connected, with this information I can connect to my networking team for any further troubleshooting issue or any changes if I required.

As I wanted to design HyperV/SCVMM solution, I was working on the same from networking part. and while architecturing Network solution for HyperV and I needed some Network side inventory like where my Windows Server HyperV Nic ports are connected on Physical switches for further designing, I don't see any separate interface or console where I can find such Information (if anyone know feel free to point out). So to find that information you can use Microsoft's tool Microsoft Network Monitor 3.4. It can capture network traffic and then you can filter the information you required. This topic is not only limited to Windows Server you can also use your own desktop to test this.

Here I will be using my favorite tool Wireshark. Wireshark is a network protocol analyzer for Unix and Windows, and it has many great features, I have download and installed it on my Windows Server., Here my server has got two physical ethernet cards and I want to know where both cards are connected on physical Switch.

Search for wireshare and open it

Once Wireshark is running, you will detect all Network cards you have in your server, It matches the earlier screenshot I posted, Now You need to select one network card at a time, first NIC card I select is Team01, It will capture traffic on Team01 Nic.

Once you click on the network card it will start analyzing traffic in and out from the Nic. and you will see tons and tons of information. Now you will need to filter this captured information to find required CDP information. Type CDP and it will drop down the list of protocols from that list select CDP, incase you need LLDP information you can filter for LLDP.

Here I have got what I wanted. Very specific useful information regarding Switch name and Switch port number.

Now I have collected information for one of the NIC card, I will be capturing data for another NIC card. from the capture menu press Stop to halt the capturing packets and go on selecting another Ethernet Card in the Options which is currently grayed out.

Now in the same Capture menu Options will be active once you stop capturing and we can click it to select another NIC.

You will again see 2 Nics in the list as we have already collected and captured information for one of the NIC in my scenario I had team01 and now will collect information for Management NIC card and click on start.

Now here is the info for another NIC card. As long as you keep wireshare capture starting and running, It will keep fetching the CDP data after some interval, Again you can capture LLDP information also with this tool.

I found some of other tools exist which only CDP from tallsoft CDP monitor which is also handy, and there is windump.exe commandline utility which is available on the wireshark only.

My earlier useful script for collecting CDP and LLDP from VMWare ESXi environment.

PowerCLI esxi host Physical nic info in nice table format

Save complete virtual PortGroup information Settings - Powercli

Powercli Pull CDP and LLDP information in single nice table format - Part 2

Error resolved: Hyperv cannot be installed: A Hyperviser is already running.

noreply@blogger.com (kunal) — Wed, 23 Mar 2016 09:59:00 +0530

From my earlier Post Powershell Rocks - Creating virtual Nic cards for testing (Standalone HyperV), While installing HyperV role I got error through Server Manager GUI I was receiving error, HyperV cannot be installed: A Hyperviser is already running. After many repetitive attempts through server manager GUI it was failing, I also used Powershell command Install-WindowsFeature Hyper-V but result was same. In the last I stumble upon Microsoft blog .

And I got to know about new command for installing optional roles.
Enable-WindowsOptionalFeature –Online -FeatureName Microsoft-Hyper-V –All
This resolved my error and after reboot I was able to use hyperV.

Old useful Posts
Configuring HyperV on windows 2008 R2 and configuring Failover clustering

Powershell Rocks - Creating virtual Nic cards for testing (Standalone HyperV)

noreply@blogger.com (kunal) — Wed, 23 Mar 2016 01:15:00 +0530

Today I had to setup some demo lab environment for my friend for tutoring purpose. He had couple of old desktop and Laptop with low configurations and one manageable old switch and router, I intended to install Windows server 2012 R2 on them and wanted to show standalone HyperV Demo. I installed and setup server everything was working fine but I wanted to show him HyperV Microsoft Failover Clustering but unable to simulate it, why because all those couple of desktops and laptop had only one NIC card and I required another Network Card for heartbeat purpose. but we didn't want to invest anything on the old. so here Powershell came to our rescue.

In windows server 2012 R2 when installed Hyperv Role and Powershell module, there is a feature you can create multiple virtual ethernet card, and all the traffic flows through single physical network card. Here I wanted to achieve my physical and virtual network card configuration like below diagram, HyperV role must be installed is requirement and Switch port where physical Nic is connected must be trunk if you want to use different subnets.

Check out my older post for configuring HyperV on windows 2008 R2 and configuring Failover clustering

Here are the Powershell commands with there parameters I used to setup and configure virtual network cards. First rule open Powershell as administrator.

Note: Running second command in the line can cause server disconnection. hence advised to not use remote desktop instead use ILO, DRAC or make sure you are in the front of server.

##*************************************************************************

Get-NetAdapter

New-NetLbfoTeam -Name "SwTeam" -TeamMembers PhysicalNic -TeamingMode Static -Confirm:$false

New-VMSwitch "VirtualSwitch" -MinimumBandwidthMode weight -NetAdapterName "SwTeam" -AllowManagement $false

Add-VMNetworkAdapter -ManagementOS -Name "Management" -SwitchName "VirtualSwitch"

Set-VMNetworkAdapter -ManagementOS -Name "Management" -MinimumBandwidthWeight 33

Add-VMNetworkAdapter -ManagementOS -Name "HeartBeat" -SwitchName "VirtualSwitch"

Set-VMNetworkAdapter -ManagementOS -Name "HeartBeat" -MinimumBandwidthWeight 33

Add-VMNetworkAdapter -ManagementOS -Name "Storage" -SwitchName "VirtualSwitch"

Set-VMNetworkAdapter -ManagementOS -Name "Storage" -MinimumBandwidthWeight 33

Get-VMNetworkAdapter -All -Name *

Get-NetAdapter

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanID 5

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "HeartBeat" -Access -VlanID 10

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Storage" -Access -VlanID 20

Get-VMNetworkAdapterVlan -ManagementOS

##*************************************************************************

Now I will be running one command at a time and whatever I will be setting parameters based on results. First I will be running Get-Netadapter which shows all the Ethernet cards on the my system. As you can see from below screenshot I got only one Physical NIC and it is named as "PhysicalNic", Which I will be require in my next cmdlets.

Now I know, What is my Physical Nic name is, which I am going to use it in next command

Note: Running this command can cause server disconnection. hence advised to not use remote desktop instead use ILO, DRAC, or make sure you are in the front of server.

New-NetLbfoTeam -Name "SwTeam" -TeamMembers PhysicalNic -TeamingMode Static -Confirm:$false

It has created new software switch "SwTeam" and PhysicalNic is part of the Team, Static is the Teaming mode I am using here.

Tip: Incase you have installed HyperV but you are not able to find above command or next command I am going to run below command to install hyperv feature before starting command. HyperV role must be installed before running above commands.

Install-WindowsFeature Hyper-V-PowerShell

New-VMSwitch "VirtualSwitch" -MinimumBandwidthMode weight -NetAdapterName "SwTeam" -AllowManagement $false

New-VMSwitch cmdlet creates a new virtual switch on one or more virtual machine hosts, Parameter minimumbandwidthMode is weight (weight is a unit (1 to 100) which i will be using in next command.)

Next I will be adding Virtual Network card and to the Host. and it will be using 33 % bandwidth weight of Physical nic. ManagementOS is your main operating system.

Add-VMNetworkAdapter -ManagementOS -Name "Management" -SwitchName "VirtualSwitch"

Set-VMNetworkAdapter -ManagementOS -Name "Management" -MinimumBandwidthWeight 33

Here is next screenshot after creating all the virtual nic cards.

Next command to verify again what we have deployed.

Get-VMNetworkAdapter -All -Name *

Get-NetAdapter

The last command is setting Vlan. and verify what settings has been configured. You can change below parameters as per your requirements.
Tip: Incase you don't have trunk port(I mean your computers are connected to normal switches), do not run below commands, just assign IP directly.

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanID 5

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "HeartBeat" -Access -VlanID 10

Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Storage" -Access -VlanID 20

Get-VMNetworkAdapterVlan -ManagementOS

Now the last step is assign IP to virtual network cards and verify you can connect them over network, here I will assign IP on Management Network and just will check whether I am able to do RDP to the server. And I am Successful.

Check out my older post for configuring HyperV on windows 2008 R2 and configuring Failover clustering

HyperV Roll installation troubleshooting Error resolved: Hyperv cannot be installed: A Hyperviser is already running.

Resolved: The trust relationship between this workstation and the primary domain failed

noreply@blogger.com (kunal) — Sun, 6 Mar 2016 12:45:00 +0530

In my earlier post I knew only 2 commands (Netdom and Test-ComputerSecureChannel) to rejoin computer in domain without restart. One of the user Tim Basten commented on my post that there is one more powershell cmdlet can be used to fix broken computer account without restart. so I tried it and yes it works perfectly.

Reset-ComputerMachinePassword -Credential (Get-Credential)

Once you execute it will ask for your domain admin username and password.

It is fairly simple. I guess their might be more commands available to do same tasks, I know there is one more from command prompt nltest but never used it.

Powershell Rocks, Rejoin computers in domain without restart

Install missing Powershell ISE on Windows Server 2008 R2

noreply@blogger.com (kunal) — Wed, 24 Feb 2016 20:31:00 +0530

Everytime I login to any of new server in my windows server 2008 r2 with default PSversion powershell v2 I find ISE is missing and it need to install in case if i want to run some script, (Powershell ISE is my favorite powershell script editor which comes with windows 2008 r2 and above), I use ISE lot to edit scripts.

Here is how when I search for powershell it is missing.

Here is how you can install it using powershell it self, open powershell as an administrator. and you will have run below 2 commands to install ISE.
Import-Module ServerManager
Add-WindowsFeature Powershell-ISE

If you check in the above screenshot you will find powershell can be used from GUI, need to install as a feature from Server Manager and the Feature name is a Windows Powershell Integrated Scripting Engine.

I prefer the powershell way only to install ISE, because I find it quick, no need to touch mouse., and also this way I memorize my essential commands.

vSphere Datastores inventory report powercli - Volume 2

noreply@blogger.com (kunal) — Fri, 19 Feb 2016 22:59:00 +0530

I used to collect datastores inventory using my old script VMware Datastores inventory. It is still very handy when I want to keep it as inventory. This inventory is also good when I want to troubleshoot, but over the period of time I found still I am missing something. Now I have added some more useful information about iSCSI paths. With this information I was able to rectify and implement multiplying best practices correctly.

Alike my old script this also tells datastore configuration information per host, It starts with first esxi host, pull information about all the datastores configured on it, then second host and all the datastores on it, and so on, Below is list this script pulls information about.

VMhost name

DatastoreName - You will find it repetitive if same datastore is mounted on another host also

FreeSpaceGB - Free Space in GB

CapacityGB - Capacity in GB

FileSystemVersion - this tells what is the version of VMFS filesystem.

RuntimeName: Handy when you want to check what device datastore is mapped.

CanonicalName: I use this to match my esxi datastore and storage name. (I can ensure I am working on correct lun/datastore)

MultipathPolicy: Self explanatory.

Vendor: Esxi can detect what can be device (vendor) of datastore.

DatastoreDatacenter: Datacenter this datastore available.

VMsOnDatastore: VMs name on the this datastore but only belongs the esxi host you are fetching information

NumberofPaths: This is really handy and saved my day lots of time.

Paths: IP addresses of Paths (iscsi target storage paths)

State: Where path is active or standby?

Preferred: What storage path is preferred path?

IsWorkingPath: This somewhat similar to preferred path. but tells is the path active currently.

This is screenshot after running the script on the console.

here is the script, on how to use u can check my previous articles,

  #####################################                                                                
  ## http://kunaludapi.blogspot.com                                                                
  ## Version: 2                                                               
  ## Date: 16 Dec 2015                                                              
  ## Script tested on below platform                                                                
  ## 1) Powershell v4                                                               
  ## 2) Powercli v5.5                                                                
  ## 3) Vsphere 5.5                                                               
  ####################################                                                               
  #Add-PSSnapin vmware.vimautomation.core                                                               
  #Connect-Viserver #vcenterserver                                                                
                                                               
 function Get-DatastoreInventory {                                                               
   $HostDatastoreInfo = Get-VMHost | Get-ScsiLun -LunType disk                                                                
   $DatastoreInfo = Get-Datastore                                                               
   foreach ($Hostdatastore in $HostDatastoreInfo) {                                                                
    $Datastore = $DatastoreInfo | Where-Object {$_.extensiondata.info.vmfs.extent.Diskname -match $Hostdatastore.CanonicalName}                                                               
    $LunPath = $Hostdatastore | Get-ScsiLunPath                                                              
    if ($Datastore.ExtensionData.vm) {                                                               
     $VMsOnDatastore = $(Get-view $Datastore.ExtensionData.vm).name -join ","                                                               
    } #if                                                               
    else {$VMsOnDatastore = "No VMs"}                                                               
                                                                 
   #Work on not assigned Luns error at silentlyContinue                                                               
    if ($Datastore.Name -eq $null) {                                                              
     $DatastoreName = "Not mapped"                                                              
     $FileSystemVersion = "Not mapped"                                                              
    }                                                              
    else {                                                              
     $DatastoreName = $Datastore.Name -join ","                                                              
     $FileSystemVersion = $Datastore[0].FileSystemVersion                                                               
    }                                                              
                                                                   
    $DatastoreFreeSpace = $Datastore.FreeSpaceGB -join ", "                                                               
    $DatastoreCapacityGB = $Datastore.CapacityGB -join ", "                                                               
    $DatastoreDatacenter = $Datastore.Datacenter -join ", "                                                               
                                                               
    $State = $LunPath.State -join ", "                                                              
    $Preferred = $LunPath.Preferred -join ", "                                                              
    $Paths = ($LunPath.ExtensionData.Transport | foreach {($_.Address -split ":")[0]}) -Join ", "                                                              
    $IsWorkingPath = $LunPath.ExtensionData.IsWorkingPath -Join ", "                                                              
                                                                  
    $Obj = New-Object PSObject                                                               
    $Obj | Add-Member -Name VMhost -MemberType NoteProperty -Value $hostdatastore.VMHost                                                               
    $Obj | Add-Member -Name DatastoreName -MemberType NoteProperty -Value $DatastoreName                                                                
    $Obj | Add-Member -Name FreeSpaceGB -MemberType NoteProperty -Value $DatastoreFreeSpace                                                               
    $Obj | Add-Member -Name CapacityGB -MemberType NoteProperty -Value $DatastoreCapacityGB                                                               
    $Obj | Add-Member -Name FileSystemVersion -MemberType NoteProperty -Value $FileSystemVersion                                                               
    $Obj | Add-Member -Name RuntimeName -MemberType NoteProperty -Value $hostdatastore.RuntimeName                                                               
    $Obj | Add-Member -Name CanonicalName -MemberType NoteProperty -Value $hostdatastore.CanonicalName                                                               
    $Obj | Add-Member -Name MultipathPolicy -MemberType NoteProperty -Value $hostdatastore.MultipathPolicy                                                               
    $Obj | Add-Member -Name Vendor -MemberType NoteProperty -Value $hostdatastore.Vendor                                                               
    $Obj | Add-Member -Name DatastoreDatacenter -MemberType NoteProperty -Value $DatastoreDatacenter                                                               
    $Obj | Add-Member -Name VMsOnDataStore -MemberType NoteProperty -Value $VMsOnDatastore                                                               
    $Obj | Add-Member -Name NumberOfPaths -MemberType NoteProperty -Value $LunPath.Count                                                              
    $Obj | Add-Member -Name Paths -MemberType NoteProperty -Value $Paths                                                              
    $Obj | Add-Member -Name State -MemberType NoteProperty -Value $State                                                              
    $Obj | Add-Member -Name Preferred -MemberType NoteProperty -Value $Preferred                                                              
    $Obj | Add-Member -Name IsWorkingPath -MemberType NoteProperty -Value $IsWorkingPath                                                              
    $Obj                                                               
   }                                                               
  }                                                               
  Get-DatastoreInventory | Export-Csv -NoTypeInformation c:\temp\DatastoreInfoHostwise.csv

I exported report to csv and file looks like this., Csv file can be opened in excel, this CSV can be used as inventory later, My favorite use is capacity management, I kept collecting data for 1 year, and after 1 year i know how datastore is getting filled gradually.

If you find this information is worth sharing please do share the knowledge.

Other useful Blogs and Scripts
Collect disk space detail and send it in email Powercli

Version 2 VM disk space detail send via email Powercli

Configuring Microsoft iSCSI Target datastore on Esxi server and multipathing Step by Step

import vCenter roles (privileges) - Powercli.

noreply@blogger.com (kunal) — Mon, 15 Feb 2016 22:04:00 +0530

From my first article Export vcenter roles (privileges) I exported all the roles and privileges successfully now it was task to migrate Roles on another vCenter. I already had grabbed roles in files so they where completely portable, I extracted zip file of my roles in the same c:\temp folder as I was going to use it.

Other very useful script for vCenter migration.

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

this is screenshot from my previous post it contains all the roles.

Here is the script. I hope I am keeping all simple.

 <#   
  .Synopsis   
   Imports roles into vsphere roles..   
  .Description   
   This script imports roles into vspheres from .role file/   
  .Example   
   Import-vSphereRoles -Path c:\temp  
   Import Roles to the folder.   
  .Notes  
   NAME: Import-vSphereRoles   
   AUTHOR: Kunal Udapi   
   LASTEDIT: 15th February 2016  
   KEYWORDS: Import Roles   
  .Link   
   #Check Online version: http://kunaludapi.blogspot.com    
   #Requires -Version 3.0   
  #>   
  #requires -Version 3    
 [CmdletBinding(SupportsShouldProcess)]   
  Param(   
   [Parameter(Mandatory=$true, Position=1,   
    ValueFromPipeline=$true)]   
   [AllowNull()]   
   [alias("LiteralPath")]   
   [string]$Path = "c:\temp"    
  ) #Param   
 Begin {  
   $roleFiles = Get-ChildItem -Path $Path -Filter *.role  
 }  
 Process {  
   foreach ($role in $roleFiles) {  
     $VIRoleName = $role.BaseName   
     $RolesContent = Get-Content -Path $role.FullName  
     New-Virole -Name $VIRoleName | Out-Null  
     Write-Host "Created Role `"$VIRoleName`"" -BackgroundColor DarkGreen  
     foreach ($Privilege in $RolesContent) {  
       if (-not($privilege -eq $null -or $privilage -eq "")) {  
         Write-Host "Setting Permissions `"$Privilege`" on Role `"$VIRoleName`"" -ForegroundColor Yellow  
         Set-VIRole -Role $VIRoleName -AddPrivilege (Get-VIPrivilege -ID $privilege) | Out-Null  
       } #if (-not($privilege -eq $null -or $privilage -eq ""))  
     } #foreach ($Privilege in $RolesContent)  
   } #foreach ($role in $roleFiles)  
 }

Once you keep it in .ps1 and run it (check my earlier post for Export vcenter roles (privileges) how i have collected information and running script), you will see powercli console some thing like below screenshot.

I will be sharing next script for Exporting and Importing roles permissions stay tuned. If you like this article please share knowledge.

Export vcenter roles (privileges) - Powercli.

noreply@blogger.com (kunal) — Mon, 15 Feb 2016 21:47:00 +0530

This post I am continuing from another posts, Migration from one vcenter to another.

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

In this post I will be showing how to export roles. and can be imported to another vCenter. This is completely dedicated to exporting roles only, they are exported to specified folder with .role extension. As you can see I have multiple roles created, some are by default created roles, my script skip those roles and only backup User created roles.

When you edit one of the role you will see information some thing like this, these are called roles privileges. Each privilege has some meaning ful name, ie inside alarms there is acknowledge alarm rights.

Here is my script that can pull all this information and keeps in .role file. Copy paste this script and keep it in ps1 file.

  <#   
  .Synopsis   
   Exports vsphere roles to text file extension roles.   
  .Description   
   This script exports only the custom created roles by users   
  .Example   
   Export-vSphereRoles -Path c:\temp  
   Exports Roles to the folder.   
  .Notes  
   NAME: Export-vSphereRoles   
   AUTHOR: Kunal Udapi   
   LASTEDIT: 12th February 2016  
   KEYWORDS: Export Roles   
  .Link   
   #Check Online version: http://kunaludapi.blogspot.com    
   #Requires -Version 3.0   
  #>   
  #requires -Version 3    
 [CmdletBinding(SupportsShouldProcess)]   
  Param(   
   [Parameter(Mandatory=$true, Position=1,   
    ValueFromPipeline=$true)]   
   [AllowNull()]   
   [alias("LiteralPath")]   
   [string]$Path = "c:\temp"    
  ) #Param   
 Begin {  
   $DefaultRoles = "NoAccess", "Anonymous", "View", "ReadOnly", "Admin", "VirtualMachinePowerUser", "VirtualMachineUser", "ResourcePoolAdministrator", "VMwareConsolidatedBackupUser", "DatastoreConsumer", "NetworkConsumer"  
   $DefaultRolescount = $defaultRoles.Count  
   $CustomRoles = @()  
 } #Begin  
   
 Process {  
   $AllVIRoles = Get-VIRole  
   
   0..($DefaultRolescount) | ForEach-Object {  
     if ($(Get-Variable "role$_" -ErrorAction SilentlyContinue)) {  
       Remove-Variable "role$_" -Force -Confirm:$false  
     } #if ($(Get-Variable "role$_" -ErrorAction SilentlyContinue))  
   } #0..($DefaultRolescount) | Foreach-Object  
   
   0..$DefaultRolescount | ForEach-Object {  
     $DefaultRolesnumber = $DefaultRoles[$_]  
     if ($_ -eq 0) {  
       New-Variable "role$_" -Option AllScope -Value ($AllVIRoles | Where-Object {$_.Name -ne $DefaultRolesnumber})  
     } #if ($_ -eq 0)  
     else {  
       $vartxt = $_ - 1  
       $lastrole = 'role'+"$vartxt"  
       #Get-Variable $lastrole  
       New-Variable "role$_" -Option AllScope -Value (Get-Variable "$lastrole" | select -ExpandProperty value | Where-Object {$_.Name -ne $DefaultRolesnumber})  
     } #else ($_ -eq 0)  
   } #0..$DefaultRolescount | ForEach-Object  
   $filteredRoles = Get-Variable "role$($DefaultRolescount-1)" | select -ExpandProperty value  
 } #Process  
 End {  
   $filteredRoles | ForEach-Object {  
     $completePath = Join-Path -Path $Path -ChildPath "$_.role"  
     Write-Host "Exporting Role `"$($_.Name)`" to `"$completePath`"" -ForegroundColor Yellow  
     $_ | Get-VIPrivilege | select-object -ExpandProperty Id | Out-File -FilePath $completePath  
   } #$filteredRoles | ForEach-Object  
 } #End

Open vmwere vsphere powercli, Make sure your execution policy is set to remote singed or something that can execute script. Mine is unrestricted, I only run script created by me only.

Connect to old vcenter server using Connect-VIServer command.

Once you are connected. time to execute command, I have saved my script under c:\script. and this is how I run that script with dot sourcing. Once you run ps1 file you can see on the screen what is happening in yellow.

All the roles file are stored on the c:\temp, now you can copy paste these roles in zip file and ready to be used on other vcenter for importing.

You can open role file in notepad and the view is as below. This is how exported vcenter role file looks like, in my next blog i am going to use same file and export privileges to another vCenter.

Change username/password configured on logon tab of Windows Service - Powershell

noreply@blogger.com (kunal) — Sat, 13 Feb 2016 15:51:00 +0530

This my another part of List account configured on logon of Windows Service and in this there is a recipe to (Setup service account) change or replace account username/ password on windows service logon tab. Before running make sure your account has permissions or admin rights to change into windows service. Also make sure you open powershell as administrator.

You can check my earlier post List account configured on logon of Windows Service, how to use this script, if you still have any issue drop a comment on this post I will try to resolve it.

 function Set-ServiceLogonAccount {  
 <#  
  .Synopsis  
   Change or set username password on Service logon Account  
  .Description  
   Make sure you open powershell with as administrator and you have appropriate permissions to modify service settings. You must specify Service name instead of display name.  
  .Example  
   Set-ServiceLogonAccount -ComputerName 192.168.33.51 -LogonUserName vcloud\vkunal -LogonPassword Computer@1 -Service lanmanserver -Credential (Get-Credential)  
     
   It make changes on service lanmanserver on remote computer 192.168.33.51, logon username is changed to vcloud\vkunal and password is set to Computer@1, credential is your remote login credentials.  
  .Example  
   Set-ServiceLogonAccount -LogonUserName .\test -LogonPassword Computer@1  
   By default if only logonusername and logonpassword paramter given it make changes to localhost and service is lanmanserver.  
   
  .OutPuts  
   ∞ JUMBOPC is pinging, attempting to connect...  
   
   PSComputerName : JUMBOPC  
   Name      : LanmanServer  
   DisplayName  : Server  
   StartMode   : Auto  
   State     : Running  
   Started    : True  
   StartName   : .\test  
   
  .Notes  
   NAME: Set-ServiceLogonAccount  
   AUTHOR: Kunal Udapi  
   LASTEDIT: 13th February 2015  
   KEYWORDS: Service log on accounts  
  .Link  
   #Check Online version: Http://kunaludapi.blogspot.com   
   #Requires -Version 3.0  
  #>  
 #requires -Version 3   
 [CmdletBinding(SupportsShouldProcess)]  
 Param(  
   [Parameter(<#Mandatory=$true,#>Position=1,  
     ValueFromPipeline=$true,  
     ValueFromPipelineByPropertyName=$true)]  
   [AllowNull()]  
   [alias("ComputerName", "Computer")]  
   [string]$Name = $env:COMPUTERNAME,   
   
   [Parameter(Mandatory=$true,Position=3)]  
   [string]$LogonUserName,   
     
   [Parameter(Mandatory=$true,Position=4)]  
   [string]$LogonPassword,   
      
   [Parameter(Position=2)]  
   [AllowNull()]    
   [alias("ServiceName")]  
   [string]$Service = 'LanmanServer',  
   
   #[Parameter(Mandatory=$true)]  
   [System.Management.Automation.PSCredential]$Credential,  
   $Protocol = 'DCOM'  
 ) #Param  
 Begin {  
   #$TempFolder = Split-Path $CSVfile  
   #if (-not (Test-Path $TempFolder)) {  
   #  [void](New-Item -Path $TempFolder -Force)  
   #} #if (-not (Test-Path $TempFolder)) {  
 #region Ping  
   Function Get-Ping {  
     Test-Connection -ComputerName $Name -Quiet -Count 2 -ErrorAction SilentlyContinue  
   } # Function Ping-Server  
 #endregion  
   $CIMoption = New-CimSessionOption -Protocol $protocol  
 } #Begin  
 Process {  
   $query = "Select * from Win32_Service Where Name = `'$service`'"  
   if ($(Get-Ping $Name) -eq $true) {  
     Write-Host "$([char]8734) $Name is pinging, attempting to connect..." -ForegroundColor Green  
     if ($Credential -eq $null) {  
       Try {  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -ErrorAction SilentlyContinue  
         $cimresult = Get-CimInstance -CimSession $CIMsession -Query $query | Invoke-CimMethod -Name Change -Arguments @{StartName=$LogonUserName;StartPassword=$LogonPassword}  
         #$ServiceDetails = Get-CimInstance -CimSession $CIMsession -Query $query  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #if ($Credential -eq $null)  
     else {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -Credential $Credential -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -Credential $Credential -ErrorAction SilentlyContinue  
         $cimresult = Get-CimInstance -CimSession $CIMsession -Query $query |Invoke-CimMethod -Name Change -Arguments @{StartName=$LogonUserName;StartPassword=$LogonPassword}  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #else ($Credential -eq $null)  
   } #if ($(Ping-Server $Name) -eq $true  
   else {  
     Write-Host "$([char]8734) $Name is not pinging, but Still trying to connect..." -ForegroundColor Yellow  
     if ($Credential -eq $null) {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -ErrorAction SilentlyContinue  
         $cimresult = Get-CimInstance -CimSession $CIMsession -Query $query |Invoke-CimMethod -Name Change -Arguments @{StartName=$LogonUserName;StartPassword=$LogonPassword}  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #if ($Credential -eq $null)  
     else {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -Credential $Credential -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -Credential $Credential -ErrorAction SilentlyContinue  
         $cimresult = Get-CimInstance -CimSession $CIMsession -Query $query |Invoke-CimMethod -Name Change -Arguments @{StartName=$LogonUserName;StartPassword=$LogonPassword}  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #else ($Credential -eq $null)  
   } #else ($(Ping-Server $Name) -eq $false)  
   if (-not ($cimresult -eq $null)) {  
     Get-CimInstance -CimSession $CIMsession -Query $query | Select-Object PSComputerName, Name, DisplayName, StartMode, State, Started, StartName  
   } #if ($ServiceDetails -eq $null)  
   else {  
     Write-Host "`t $([char]215) Please check Server $Name manually" -ForegroundColor Red  
   } #else ($ServiceDetail -eq $null)  
 } #Process  
 End {  
   
 } #End  
 } $function

In the first screenshot I am setting local account on local machine,

In this screenshot I am modifying logon account on remote server, service is lanmanserver, also I have mention credential which will popup for username password to connect to remote server.

Here is parameters information
-ComputerName: If not specified default is localhost (this syntex can take value from pipe as well)
-LogonUserName: Service account username
-LogonPassword: Service Account password
-Service: if not specified default is lanmanserver, you have mention service name not display name
This is final result from both local and remote computer from services.msc
-Credential: Incase if remote computer in another domain or if you are not administrator you can use "-credential (get-credential)" to connect. otherwise for same domain this parameter doesn't required.
-Protocol: By default it uses legacy wmi dcom protocol to connect, there is another option wsman which use PSRemoting protocol.

Check on earlier useful script:
Get members from Remote Groups

Add or Remove members from Remote Group

Change username/password configured on logon tab of Windows Service

List account configured on logon of Windows Service - Powershell

noreply@blogger.com (kunal) — Tue, 26 Jan 2016 13:56:00 +0530

Maintaining best practices on windows best thing, but when someone configures it incorrectly, it is hard to track those mis-configured item., you have to check through all the settings in documents and it is manually time consuming boring task. I had a scenario where other engineer used his username password on local services account in Services, and he left the organization or is on leave (password expired), causing services to stop, and critical application is down in the absence of user, and you have to take all the heat.

Here is the script, helps to find or list accounts configured in the windows services. and are the following parameters to the scripts.
-ComputerName: If not specified default is localhost
-Service: if not specified default is lanmanserver, you have mention service name not display name

-Credential: Incase if remote computer in another domain or if you are not administrator you can use "-credential (get-credential)" to connect. otherwise for same domain this parameter doesn't required.
-Protocol: By default it uses legacy wmi dcom protocol to connect, there is another option wsman which use PSRemoting protocol.

 function Get-ServiceAccount {  
 <#  
  .Synopsis  
   Get the log on account configured in windows service.  
  .Description  
   The Get-ServiceAccount command collects log on account user configured in windows service. you will have to use servicename (not service display name) in the service parameter  
  .Example  
   Get-ServiceAccount  
   It will show log on account configured of the lanmanserver service.  
  .Example  
   "ServiceName" | Get-ServiceAccount  
   Cat c:\temp\Computerlist.txt | Get-ServiceAccount  
   Get-ServiceAccount is capable of taking output pipeline.  
   Get-ServiceAccount -Service wuauserv -Credential (Get-Credential) -ComputerName Server001  
   ∞ Server001 is pinging, attempting to connect...  
   PSComputerName : Server001  
   Name      : wuauserv  
   DisplayName  : Windows Update  
   StartMode   : Manual  
   State     : Running  
   Started    : True  
   StartName   : LocalSystem  
  .Example  
   Get-ServiceAccount -Service wuauserv -Credential (Get-Credential) -ComputerName Server001 -Protocol WSMAN   
   It collects the information using wsman protocol  
  .Example  
   "Server001", "server002", "Server003" | foreach {Get-ServiceAccount -Service someservice -ComputerName $_}  
   Get-Content -Path c:\temp\serverlist.txt | foreach {Get-ServiceAccount -Service someservice -ComputerName $_}  
   you can use it to featch information from multiple computers.  
  .Example  
   $cred = (Get-Crendential)  
   "Server001", "Server002" | foreach {Get-ServiceAccount -Computer $_ -Credential $cred -Service someservice}  
   Servers can be passed from array or files, and you can specify crendetials  
  .Parameter ComputerName  
   It is Alias to Name parameter  
   if kept blank by default will collect information about Localhost.  
  .Parameter Service  
   if kept blank by default will collect information about lanmanserver.  
  .Inputs  
   [string]  
  .OutPuts  
   Get-ServiceAccount -Service wuauserv -Credential (Get-Credential) -ComputerName 192.168.33.51  
   cmdlet Get-Credential at command pipeline position 1  
   Supply values for the following parameters:  
   ∞ 192.168.33.51 is pinging, attempting to connect...  
   PSComputerName : 192.168.33.51  
   Name      : wuauserv  
   DisplayName  : Windows Update  
   StartMode   : Manual  
   State     : Running  
   Started    : True  
   StartName   : LocalSystem  
  .Notes  
   NAME: Get-ServiceAccount  
   AUTHOR: Kunal Udapi  
   LASTEDIT: 26th August 2015  
   KEYWORDS: Service log on accounts  
  .Link  
   #Check Online version: Http://kunaludapi.blogspot.com   
   #Requires -Version 3.0  
  #>  
 #requires -Version 3   
 [CmdletBinding(SupportsShouldProcess)]  
 Param(  
   [Parameter(<#Mandatory=$true,#>Position=1,  
     ValueFromPipeline=$true,  
     ValueFromPipelineByPropertyName=$true)]  
   [AllowNull()]  
   [alias("ComputerName", "Computer")]  
   [string]$Name = $env:COMPUTERNAME,   
   [Parameter(Position=2)]  
   [AllowNull()]    
   [alias("ServiceName")]  
   [string]$Service = 'LanmanServer',  
   <#[Parameter(Mandatory=$true)]#$Credential#>  
   [System.Management.Automation.PSCredential]$Credential,  
   #[String]$CSVfile = "C:\Temp\ServiceDetails.csv",  
   $Protocol = 'DCOM'  
 ) #Param  
 Begin {  
   #$TempFolder = Split-Path $CSVfile  
   #if (-not (Test-Path $TempFolder)) {  
   #  [void](New-Item -Path $TempFolder -Force)  
   #} #if (-not (Test-Path $TempFolder)) {  
 #region Ping  
   Function Get-Ping {  
     Test-Connection -ComputerName $Name -Quiet -Count 2 -ErrorAction SilentlyContinue  
   } # Function Ping-Server  
 #endregion  
   $CIMoption = New-CimSessionOption -Protocol $protocol  
 } #Begin  
 Process {  
   $query = "Select * from Win32_Service Where Name = `'$service`'"  
   if ($(Get-Ping $Name) -eq $true) {  
     Write-Host "$([char]8734) $Name is pinging, attempting to connect..." -ForegroundColor Green  
     if ($Credential -eq $null) {  
       Try {  
         #$ServiceDetails = Get-WmiObject -Query $query -ComputerName $Name -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -ErrorAction SilentlyContinue  
         $ServiceDetails = Get-CimInstance -CimSession $CIMsession -Query $query  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #if ($Credential -eq $null)  
     else {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -Credential $Credential -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -Credential $Credential -ErrorAction SilentlyContinue  
         $ServiceDetails = Get-CimInstance -CimSession $CIMsession -Query $query  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #else ($Credential -eq $null)  
   } #if ($(Ping-Server $Name) -eq $true  
   else {  
     Write-Host "$([char]8734) $Name is not pinging, but Still trying to connect..." -ForegroundColor Yellow  
     if ($Credential -eq $null) {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -ErrorAction SilentlyContinue  
         $ServiceDetails = Get-CimInstance -CimSession $CIMsession -Query $query  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #if ($Credential -eq $null)  
     else {  
       Try {  
         #$ServiceDetail = Get-WmiObject -Query $query -ComputerName $Name -Credential $Credential -ErrorAction SilentlyContinue  
         $CIMsession = New-CimSession -ComputerName $Name -SessionOption $CIMoption -Credential $Credential -ErrorAction SilentlyContinue  
         $ServiceDetails = Get-CimInstance -CimSession $CIMsession -Query $query  
       } #Try  
       Catch {  
         Write-Host "`t $([char]215) Server $Name cannot be contacted, skipped it" -ForegroundColor Red  
         Continue  
       } #Catch  
     } #else ($Credential -eq $null)  
   } #else ($(Ping-Server $Name) -eq $false)  
   if (-not ($ServiceDetails -eq $null)) {  
     $ServiceDetails | Select-Object PSComputerName, Name, DisplayName, StartMode, State, Started, StartName  
   } #if ($ServiceDetails -eq $null)  
   else {  
     Write-Host "`t $([char]215) Please check Server $Name manually" -ForegroundColor Red  
   } #else ($ServiceDetail -eq $null)  
 } #Process  
 End {  
 } #End  
 } $function  
 Get-ServiceAccount

Using this script is fairly simple you can copy paste this code in Powershell profile, on how to use powershell profile you can check my another post here., In case if you don,t want to save it in profile, you can copy paste it in text file and rename extension to .ps1. and on the last line of .ps1 file put line Get-ServiceAccount to execute this function, and execute it in powershell doing dot sourcing file ie: .\script.ps1 (Before executing make sure you have run as administrator powershell and Set-ExecutionPolicy RemoteSigned (or bypass or unrestricted))

Here is the example how I can use this script for multiple servers
$cred = Get-Credential
Get-Content -Path c:\temp\Serverslist.txt | #Serverslist.txt contains list of servers
foreach {Get-ServiceAccount -Credential $cred -ComputerName $_ -Service someservice} |
Export-Csv -NoTypeInformation -Path c:\temp\ServiceInfo.csv
#You will need to make changes at the text marked in orange as per your need.

Above are some of the screenshots, checke out my next script changing username and password of the service logon.
Other useful scripts:
Get members from Remote Groups

Add or Remove members from Remote Group

Change username/password configured on logon tab of Windows Service

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

noreply@blogger.com (kunal) — Wed, 20 Jan 2016 09:18:00 +0530

As in the earlier blog after exporting VM annotations, notes and other useful information to CSV/excel file, It was time to Import those information on new vCenter, This new vCenter has new Esxi Server connected from old vCenter, and when I check Virtual Machine tab at the right side on the esxi, I don't see any Information which I had present from old vCenter.

I created VM annotation attributes, just to show you how data is missing and everything is blank., This how you miss value vm annotation information after moving esxi to another vcenter

This information can be filled with below script.

 function Import-VMAnnotation {  
 <#   
 .SYNOPSIS   
 Import VM information Annotation, Notes into VM Attributes  
 .DESCRIPTION   
 The function set Annotation, Notes on VM into vcenter, you will require Export-VMAnnotation function to export data into CSV file.  
 .NOTES    
 Author: Kunal Udapi   
 http://kunaludapi.blogspot.com   
 .PARAMETER N/a   
 No Parameters Required   
 .EXAMPLE   
 PS> Import-VMAnnotation -CSV c:\Temp\VMCMDB.csv   
 #>   
 [CmdletBinding()]  
 #####################################    
 ## ## Version: 1    
 ## Tested this script on successfully   
 ## 1) Powershell v4    
 ## 2) Windows 8.1  
 ## 3) vSphere 5.5 (vcenter, esxi)  
 ## 4) powercli 6.0  
 #####################################    
 Param (  
   [Parameter(Mandatory=$true, Position=0)]   
   [ValidateNotNullOrEmpty()]   
   [string]$CSV  
 )  
   Begin{  
    if (-not(Get-PSSnapin vmware.vimautomation.core -ErrorAction SilentlyContinue)) {   
     Add-PSSnapin vmware.vimautomation.core   
    } #if   
   } #Begin  
   Process{  
     $vmlist = Import-Csv $CSV  
     $NonRequiredProperties = ""  
     $properties = $vmlist | Get-Member -MemberType NoteProperty | Where-Object {($_.name -ne "VMName") -and ($_.name -ne "PowerState") -and ($_.name -ne "IPAddress") -and ($_.name -ne "FolderPath") -and ($_.name -ne "Notes")} | Select -ExpandProperty Name  
     $CustomAttributes = Get-CustomAttribute -TargetType VirtualMachine  
     foreach ($NotExist in $properties) {  
       if (!($CustomAttributes.Name -contains $Notexist)) {  
         Write-Host -BackgroundColor Yellow -ForegroundColor Black "###Custom Attribute `"$NotExist`" does not exist Creating it###"  
         [void](New-CustomAttribute -Name $NotExist -TargetType VirtualMachine)  
       } #if (-Not($CustomAttributes -contains $Notexist))  
       else {  
         Write-Host -BackgroundColor DarkGreen "###Custom Attribute `"$NotExist`" exists, Skipping it###"  
       } #else (!($CustomAttributes.Name -contains $Notexist))  
     } #foreach ($NotExist in $properties)  
     Foreach ($VMObj in $VMList) {  
       $vm = Get-VM $VMObj.VMName  
       #$VMObj.VMName  
       Write-Host -BackgroundColor DarkGreen "`t###Adding Notes and Annotation on Virtual Machine `"$Name`"###"  
       [void]($vm | Set-VM -Notes $($VMObj.notes) -Confirm:$false)  
       $Name = $vm.name  
       Foreach ($Prop in $properties) {  
         $PropValue = $VMObj.$prop        
           Write-Host -BackgroundColor Yellow -ForegroundColor Black "`t`t###Adding value `"$PropValue`" to Attribute `"$prop`"###"  
           [void]($VM | Set-Annotation -CustomAttribute $Prop -Value $Propvalue)  
       } #Foreach ($Prop in $properties)  
     } #Foreach ($VM in $VMList)  
   } #Process  
   End{  
   } #End  
 }

Using this script is fairly simple you can copy paste this code in Powershell profile, on how to use powershell profile you can check my another post here., In case if you don,t want to save it in profile, you can copy paste it in text file and rename extension to .ps1. and on the last line of .ps1 file put line Import-VMAnnotation -CSV c:\temp\VMCMDB.csv to execute this function, and execute it in powershell doing dot sourcing file ie: .\script.ps1 (Before executing make sure you have run as administrator powershell and Set-ExecutionPolicy RemoteSigned (or bypass or unrestricted))

This script requires earlier imported annotation CSV file, no modification in csv file required it should be as it is. and execute function with below command.
Import-VMAnnotation -CSV c:\temp\VMCMDB.csv

Once the script is executed you can see results as on the screen. you don't have to even create vm Annotation attribute, this script take care of it.

I can see the all old information on new vCenter under vm annotations and notes.

If you find this article informative please do share the knowledge.
Other useful articles on importing and exporting VM information

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

noreply@blogger.com (kunal) — Mon, 18 Jan 2016 23:34:00 +0530

As I wanted to retain all the configuration and Information about VMs from previous vCenter and apply the same information on another vCenter - (Migration is about moving from Windows vCenter 5.5 to vCenter application linux 6.0 based for testing purpose), I was doing some Esxi migration to another vCenter and earlier I had written 2 script to Get Virtual machine folder Path from and VMs and Templates and Move them to the exact same folder hierarchy on another vcenter.

For small projects where there is no CMDB (Configuration Management Database) Tool is not available, you can maintain your poor mans CMDB in vCenter to fill up information about VMs and hosts or any other object, and can be used it to track information, I have implemented this process in office and made it mandatory for colleagues. Whenever VM is created, Annotation and Notes must be filled with the information (ask project team). This way I don't have to look out or ask project team about VM info every time I need. This is good for time begin CMDB tools not exist, or tools in implementation phase, and it helped me lot in the past by maintaining this data.

Back to exporting Annotation and Notes, This is the script I written today, to get the information, My annotation consist, Application Info, Contact No and Email of the team or owner of VM, Environment whether Production, Critical. Maintenance Windows (Very useful one), Project and Sub project, Notes consist any setting or any other useful information about VM. In case if your annotation attributes does match the names I have, it doesn't matter, My script can pull the information in nice CSV view.
Once you export the info to CSV you can check Import-VMAnnotation script to import information into new vCenter.

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

This is the script:

 function Export-VMAnnotation {  
   <#   
   .SYNOPSIS   
   Export VM information Folderpath, Annotation Notes  
   .DESCRIPTION   
   The function retrives folderPath, Annotation, Notes from vcenter, it can be exported to csv file.  
   .NOTES    
   Author: Kunal Udapi   
   http://kunaludapi.blogspot.com   
   .PARAMETER N/a   
   No Parameters Required   
   .EXAMPLE   
   PS> Export-VMAnnotation -Datacenter DatacenterName   
   .EXAMPLE   
   PS> Export-VMAnnotation -Datacenter DatacenterName | Export-CSV -Path c:\Temp\VMCMDB.csv  
   #>   
   [CmdletBinding()]  
   #####################################    
   ## ## Version: 1    
   ## Tested this script on successfully   
   ## 1) Powershell v4    
   ## 2) Windows 8.1  
   ## 3) vSphere 5.5 (vcenter, esxi)  
   ## 4) powercli 6.0  
   #####################################    
   Param (  
     [Parameter(Mandatory=$true, ValueFromPipelineByPropertyName=$true, Position=0)]   
     [ValidateNotNullOrEmpty()]   
     [Alias("Name")]   
     [string]$DataCenter  
   )  
   Begin {  
     if (-not(Get-PSSnapin vmware.vimautomation.core -ErrorAction SilentlyContinue)) {  
       Add-PSSnapin vmware.vimautomation.core  
     } #if  
     function Get-VMFolderPath {   
      <#   
      .SYNOPSIS   
      Get folder path of Virtual Machines   
      .DESCRIPTION   
      The function retrives complete folder Path from vcenter (Inventory >> Vms and Templates)   
      .NOTES    
      Author: Kunal Udapi   
      http://kunaludapi.blogspot.com   
      .PARAMETER N/a   
      No Parameters Required   
      .EXAMPLE   
      PS> Get-VM vmname | Get-VMFolderPath   
      .EXAMPLE   
      PS> Get-VM | Get-VMFolderPath   
      .EXAMPLE   
      PS> Get-VM | Get-VMFolderPath | Out-File c:\vmfolderPathlistl.txt   
      #>   
      #####################################    
      ## http://kunaludapi.blogspot.com    
      ## Version: 1    
      ## Windows 8.1    
      ## Tested this script on    
      ## 1) Powershell v4    
      ## 2) VMware vSphere PowerCLI 6.0 Release 1 build 2548067    
      ## 3) Vsphere 5.5    
      #####################################    
       Begin {} #Begin   
       Process {   
        foreach ($vm in $Input) {   
         $DataCenter = $vm | Get-Datacenter   
         $DataCenterName = $DataCenter.Name   
         $VMname = $vm.Name   
         $VMParentName = $vm.Folder   
         if ($VMParentName.Name -eq "vm") {   
          $FolderStructure = "{0}\{1}" -f $DataCenterName, $VMname   
          $FolderStructure   
          Continue   
         }#if ($VMParentName.Name -eq "vm")   
         else {   
          $FolderStructure = "{0}\{1}" -f $VMParentName.Name, $VMname   
          $VMParentID = Get-Folder -Id $VMParentName.ParentId   
          do {   
           $ParentFolderName = $VMParentID.Name   
           if ($ParentFolderName -eq "vm") {   
            $FolderStructure = "$DataCenterName\$FolderStructure"   
            $FolderStructure   
            break   
           } #if ($ParentFolderName -eq "vm")   
           $FolderStructure = "$ParentFolderName\$FolderStructure"   
           $VMParentID = Get-Folder -Id $VMParentID.ParentId   
          } #do   
          until ($VMParentName.ParentId -eq $DataCenter.Id) #until   
         } #else ($VMParentName.Name -eq "vm")   
        } #foreach ($vm in $VMList)   
       } #Process   
       End {} #End   
      } #function Get-VMFolderPath    
   } #Begin  
   Process {  
     $VMList = Get-Datacenter $DataCenter | Get-VM  
     foreach ($vm in $VMList) {  
               $Annotation = $vm | Get-Annotation  
       $IPAddress = $vm.extensiondata.guest.ipaddress -Join ", "  
               $FolderPath = $vm | Get-VMFolderPath  
       $InfoObj = New-Object PSObject  
       $InfoObj | Add-Member -MemberType NoteProperty -Name VMNAME -Value $vm.Name  
               $InfoObj | Add-Member -MemberType NoteProperty -Name IPAddress -Value $IPAddress  
       $InfoObj | Add-Member -MemberType NoteProperty -Name PowerState -Value $vm.Powerstate  
       $InfoObj | Add-Member -MemberType NoteProperty -Name FolderPath -Value $FolderPath  
       $InfoObj | Add-Member -MemberType NoteProperty -Name Notes -Value $vm.Notes  
       foreach ($Attr in $Annotation) {  
         $InfoObj | Add-Member -MemberType NoteProperty -Name $($Attr.Name) -Value $Attr.Value  
       }  
               $InfoObj  
     } #foreach $vm  
   } #Process  
   end {}  
 }#function Export-VMAnnotation

Using this script is fairly simple you can copy paste this code in Powershell profile, on how to use powershell profile you can check my another post here., In case if you don,t want to save it in profile, you can copy paste it in text file and rename extension to .ps1. and on the last line of .ps1 file put line Export-VMAnnotation to execute this function, and execute it in powershell doing dot sourcing file ie: .\script.ps1 (Before executing make sure you have run as administrator powershell and Set-ExecutionPolicy RemoteSigned (or bypass or unrestricted))

Once the function executated as below, You will see results on console.
Export-VMAnnotation -Datacenter DatacenterName

If you want to export information to CSV (excel). You can execute
Export-VMAnnotation -Datacenter DatacenterName | Export-CSV -Path C:\Temp\VMCMDB.csv

It pulls below information additionally, and doesn't require any changes in the original script.
VMName,
IPAddress
PowerState
FolderPath (This is my earlier script I have used to pull information)
VM notes
VM annotation and Attribution.

Although I had written sepearte article for folderpath but I wanted to keep all incormation in same file.I hope this is been informative, Stay tuned for my another script on importing VM notes and annotation in another vCenter.

Other useful information on migration

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

Move/Migrate VMs to folder Path on another vCenter - Powercli

noreply@blogger.com (kunal) — Fri, 15 Jan 2016 13:08:00 +0530

This is my second post in the 2016, first post was about Getting VMs folder Path from VMs and Templates vCenter., Which helped me to backup those VMs folder path from VMs and template, but the next task was to move vms to its respective folder.

This is the script I used to migrate VMs to folder path, You can check on how to keep this function in Powershell profile from my earlier post. Also make sure you have already got vms folder path before moving esxi to new vcenter and list is in text file as shown earlier.

 function Move-VMtoFolderPath {  
 <#  
 .SYNOPSIS  
 Move VM to folder path  
 .DESCRIPTION  
 The function retrives complete folder Path from vcenter (Inventory >> Vms and Templates)  
 .NOTES   
 Author: Kunal Udapi  
 http://kunaludapi.blogspot.com  
 .PARAMETER N/a  
 No Parameters Required  
 .EXAMPLE  
  PS> Get-Content -Path c:\temp\VmFolderPathList.txt | Move-VMtoFolderPath  
 #>  
  #####################################    
  ## http://kunaludapi.blogspot.com    
  ## Version: 1    
  ##    
  ## Tested this script on    
  ## 1) Powershell v4    
  ## 2) VMware vSphere PowerCLI 6.0 Release 1 build 2548067    
  ## 3) Vsphere 5.5    
  #####################################    
   Foreach ($FolderPath in $Input) {  
     $list = $FolderPath -split "\\"  
     $VMName = $list[-1]  
     $count = $list.count - 2  
     0..$count | ForEach-Object {  
          $number = $_  
       if ($_ -eq 0 -and $count -gt 2) {  
               $Datacenter = Get-Datacenter $list[0]  
          } #if ($_ -eq 0)  
       elseif ($_ -eq 0 -and $count -eq 0) {  
               $Datacenter = Get-Datacenter $list[$_]  
               #VM already in Datacenter no need to move  
         Continue  
       } #elseif ($_ -eq 0 -and $count -eq 0)  
       elseif ($_ -eq 0 -and $count -eq 1) {  
         $Datacenter = Get-Datacenter $list[$_]  
       } #elseif ($_ -eq 0 -and $count -eq 1)  
       elseif ($_ -eq 0 -and $count -eq 2) {  
         $Datacenter = Get-Datacenter $list[$_]  
       } #elseif ($_ -eq 0 -and $count -eq 2)  
          elseif ($_ -eq 1) {  
               $Folder = $Datacenter | Get-folder $list[$_]  
          } #elseif ($_ -eq 1)  
          else {  
         $Folder = $Folder | Get-Folder $list[$_]  
          } #else  
     } #0..$count | foreach  
     Move-VM -VM $VMName -Destination $Folder  
   } #Foreach ($FolderPath in $VMFolderPathList)  
 }#function Set-FolderPath

Next is login to new vcenter using powercli and execute. (Make sure you have datacenter, and folder names are same on other vCenter, and created them time ahead, so you dont miss the thing and retain all the folder structure as it is)
Get-Content -Path c:\temp\VmFolderPathList.txt | Move-VMtoFolderPath

Once executed, you will see what vms has been moved.

You can also monitor tasks in vCenter to view what is going on.

once everything is fine, you will see actual result in VMs and template under Inventory, all the vms moved to its respective folder.

Other Useful blogs

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

Get vCenter VM folder Path from VMs and Templates- Powercli

noreply@blogger.com (kunal) — Fri, 15 Jan 2016 12:45:00 +0530

Next blog: Move/Migrate VMs to folder Path on another vCenter - Powercli

Recently I was involved with moving/ migrating ESXi server from one vcenter to another vcenter, (Migration is about moving from Windows vCenter 5.5 to vCenter application linux 6.0 based for testing purpose) Everything was smooth, but I found, I lost my Folders and hierarchy in VMs and Template view in new vCenter. To resolve this issue, one has to note down all my folders path for VMs. and replicate the same setup on new vCenter. and then move those VMs to folders respectively. To automate and to retain the same folder settings I wrote this script. It helps me to backup and save the complete folder path of VM in text file and I can later use it to restore or move VMs to those path accurately.

Below is the code for Getting VMFolderPath

 function Get-VMFolderPath {  
 <#  
 .SYNOPSIS  
 Get folder path of Virtual Machines  
 .DESCRIPTION  
 The function retrives complete folder Path from vcenter (Inventory >> Vms and Templates)  
 .NOTES   
 Author: Kunal Udapi  
 http://kunaludapi.blogspot.com  
 .PARAMETER N/a  
 No Parameters Required  
 .EXAMPLE  
  PS> Get-VM vmname | Get-VMFolderPath  
 .EXAMPLE  
  PS> Get-VM | Get-VMFolderPath  
 .EXAMPLE  
  PS> Get-VM | Get-VMFolderPath | Out-File c:\vmfolderPathlistl.txt  
 #>  
  #####################################    
  ## http://kunaludapi.blogspot.com    
  ## Version: 1    
  ## Windows 8.1   
  ## Tested this script on    
  ## 1) Powershell v4    
  ## 2) VMware vSphere PowerCLI 6.0 Release 1 build 2548067    
  ## 3) Vsphere 5.5    
  #####################################    
   Begin {} #Begin  
   Process {  
     foreach ($vm in $Input) {  
       $DataCenter = $vm | Get-Datacenter  
       $DataCenterName = $DataCenter.Name  
       $VMname = $vm.Name  
       $VMParentName = $vm.Folder  
       if ($VMParentName.Name -eq "vm") {  
         $FolderStructure = "{0}\{1}" -f $DataCenterName, $VMname  
         $FolderStructure  
         Continue  
       }#if ($VMParentName.Name -eq "vm")  
       else {  
         $FolderStructure = "{0}\{1}" -f $VMParentName.Name, $VMname  
         $VMParentID = Get-Folder -Id $VMParentName.ParentId  
         do {  
           $ParentFolderName = $VMParentID.Name  
           if ($ParentFolderName -eq "vm") {  
             $FolderStructure = "$DataCenterName\$FolderStructure"  
             $FolderStructure  
             break  
           } #if ($ParentFolderName -eq "vm")  
           $FolderStructure = "$ParentFolderName\$FolderStructure"  
           $VMParentID = Get-Folder -Id $VMParentID.ParentId  
         } #do  
         until ($VMParentName.ParentId -eq $DataCenter.Id) #until  
       } #else ($VMParentName.Name -eq "vm")  
     } #foreach ($vm in $VMList)  
   } #Process  
   End {} #End  
 } #function Get-VMFolderPath

You can keep this code in your powershell profile. I have given steps editing Profile in this post. Once you setup profile, login into vcenter using powercli, and run below command.

Get-VM | Get-VMFolderPath | Out-File c:\temp\VmFolderPathList.txt

Above is the screenshot of notepad results, if you are not specifying out-file and showing results on console below is the screenshot.

My next blog will be about how to restore or move Vms to their respective folders on another vCenter.

Move/Migrate VMs to folder Path on another vCenter - Powercli

Other Useful blogs

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Get vCenter VM folder Path from VMs and Templates- Powercli

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Import vCenter roles (privileges) - Powercli

Export vcenter roles (privileges)

Save complete virtual PortGroup information Settings - Powercli

noreply@blogger.com (kunal) — Wed, 30 Dec 2015 14:06:00 +0530

This script I have written to pull information from all the Virtual PortGroup on esxi/vcenter and data is saved in a single CSV file, You can use it as a backup also, It is very helpful when modifying, analysing Portgroup configuration, If you take the portgroup backup with this script frequently you can even tell what are the changes done last time or compare those settings. This has saved my lots of time while troubleshooting my Virtual Standard Switch networking.

Earlier script for collecting networking information
PowerCLI esxi host Physical nic info in nice table format

Powercli Pull CDP and LLDP information in single nice table format - Part 2

Find CDP or LLDP information on Windows Servers

Below are the settings captured and stored in CSV file.

Esxi server name
PortGroup Name, This will be per esxi server not the common one
Vlan Id configured on PortGroup
vSwitch name Portgroup resides
PortGroup Type (vmkernel or Virtual Machines)
Mac Address (If portgroup is virtual machine, Mac address of all virtual machines, else mac address of vmkernel portgroup)
PortGroup Security Settings (Promiscuous mode, Mac address Changes, forged transmits)
NicTeaming Settings (Whether they are inherited from vSwitch)
Notify Switches
Failback, order
Active Nics, Standby Nics, Unused Nics
Virtual machines count on the portgroup and their name, Ip address,
PortGroup Binding compliance
MTU Settings
Management, vMotion, Ft, vSan enabled for vmkernel portgroup

This is the first screenshot when I am running script, It will collect all the virtual portgroup on the esxi in vCenter and then will collect and store information from each PortGroup in CSV file.

This is the second screenshot I want to show how the data will look like on the console. Some of the information will be blank depending on if portgroup is VMKernel or virtual machines.

Copy paste below code in text file and rename extension to .ps1

 <#  
 .SYNOPSIS  
  Gets the complete virtual portgroup information  
 .DESCRIPTION  
  This script creates a report of complete virtual portGroup information  
  of the vm’s guest OS  
 .NOTES  
  Find more information on http://kunaludapi.blogspot.com  
  Make sure you have installed Powercli and can connect to vcenter.  
 .EXAMPLE  
  PS C:\Temp> .\Get-VirtualPortGroupInfo.ps1  
 .EXAMPLE  
  PS C:\Temp> .\Get-VirtualPortGroupInfo.ps1 | Export-Csv -NoTypeInformation -Path C:\Temp\NetworkInformation.csv  
 #>  
   
  #####################################    
  ## http://kunaludapi.blogspot.com    
  ## Version: 1    
  ##    
  ## Tested this script on    
  ## 1) Powershell v4    
  ## 2) VMware vSphere PowerCLI 6.0 Release 1 build 2548067   
  ## 3) Vsphere 5.5    
  #####################################    
 Begin {  
 if (-not(Get-PSSnapin vmware.vimautomation.core -ErrorAction SilentlyContinue)) {  
   Add-PSSnapin vmware.vimautomation.core -ErrorAction SilentlyContinue  
 }  
 $report = @()  
 $IPregex=‘(?<Address>((25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?))’  
 $VMHosts = Get-VMHost  
 } #begin  
 Process {  
   foreach ($esxi in $VMHosts) {  
   Write-Host "Collecting PortGroups from Esxi Server `"$($esxi.Name)`"" -BackgroundColor DarkGreen  
   
   #All PortGroups in esxi server  
   $PortGroup = $esxi | Get-VirtualPortGroup  
     
   #iSCSI software adapter on esxi  
   $iSCSIHBA = $esxi | Get-VMHostHba -Device $HBA -Type iSCSI | Where-Object {$_.Model -eq "iSCSI Software Adapter"}  
   
   #All VMKernel Ports on esxi Server  
   $VMkernelPorts = $esxi | Get-VMHostNetworkAdapter -Name vmk*  
   
   #Esxicli information of esxi server  
   $esxcli = $esxi | Get-EsxCli  
   
     foreach ($Group in $PortGroup) {  
       Write-Host "`tFetching Info from Portgroup `"$($Group.Name)`"" -ForegroundColor Yellow  
         
       $Obj = New-Object psobject  
       $Obj | Add-Member -Name EsxiName -MemberType NoteProperty -Value $esxi.Name  
       $Obj | Add-Member -Name PortGroup -MemberType NoteProperty -Value $Group.Name  
       $Obj | Add-Member -Name VLanId -MemberType NoteProperty -Value $Group.VLanId  
       $Obj | Add-Member -Name vSwitch -MemberType NoteProperty -Value $Group.VirtualSwitchName  
         
       #Find whether PortGroup is VMKernel or VirtualMachine  
       if ($VMkernelPorts.PortGroupName -contains $group.Name) {  
         $Portgrouptype = "VMKernel"  
       } #if ($VMkernelPorts.PortGroupName -contains $group.Name)  
       else {  
         $Portgrouptype = "VirtualMachine"  
       } #else #if ($VMkernelPorts.PortGroupName -contains $group.Name)  
         $Obj | Add-Member -Name PortGroupType -MemberType NoteProperty -Value $Portgrouptype  
       
       $Macs = $Group.ExtensionData.port.mac -join ", "  
         $Obj | Add-Member -Name Mac -MemberType NoteProperty -Value $Macs  
       
       $Obj | Add-Member -Name AllowPromiscuous -MemberType NoteProperty -Value $Group.ExtensionData.ComputedPolicy.security.AllowPromiscuous  
       $Obj | Add-Member -Name MacChanges -MemberType NoteProperty -Value $Group.ExtensionData.ComputedPolicy.security.MacChanges  
       $Obj | Add-Member -Name ForgedTransmits -MemberType NoteProperty -Value $Group.ExtensionData.ComputedPolicy.security.ForgedTransmits  
   
       #Teaming Policy  
       $NicTeamingPolicy = Get-NicTeamingPolicy -VirtualPortGroup $Group  
         $Obj | Add-Member -Name IsLoadBalancingInherited -MemberType NoteProperty -Value $NicTeamingPolicy.IsLoadBalancingInherited  
       
       $LoadBalancing = $Group.ExtensionData.ComputedPolicy.NicTeaming.Policy  
         switch ($LoadBalancing)   
           {   
             loadbalance_ip {$LoadBalancingPolicy = "Route based on IP hash"}   
             loadbalance_srcmac {$LoadBalancingPolicy = "Route based on source MAC hash"}   
             loadbalance_srcid {$LoadBalancingPolicy = "Route based on the source of the port ID"}   
             failover_explicit {$LoadBalancingPolicy = "use explicity failover order"}   
             default {$LoadBalancingPolicy = "Can't Determine"}  
           } #switch ($LoadBalancing)  
         $Obj | Add-Member -Name LoadBalancing -MemberType NoteProperty -Value $LoadBalancingPolicy  
       
       $Obj | Add-Member -Name IsNetworkFailoverDetectionInherited -MemberType NoteProperty -Value $NicTeamingPolicy.IsNetworkFailoverDetectionInherited  
       $Obj | Add-Member -Name NetworkFailoverDetection -MemberType NoteProperty -Value $NicTeamingPolicy.NetworkFailoverDetectionPolicy  
       $Obj | Add-Member -Name IsNotifySwitchesInherited -MemberType NoteProperty -Value $NicTeamingPolicy.IsNotifySwitchesInherited  
       $Obj | Add-Member -Name NotifySwitches -MemberType NoteProperty -Value $Group.ExtensionData.ComputedPolicy.NicTeaming.NotifySwitches  
       $Obj | Add-Member -Name IsFailbackInherited -MemberType NoteProperty -Value $NicTeamingPolicy.IsFailbackInherited  
       $Obj | Add-Member -Name Failback -MemberType NoteProperty -Value $Group.ExtensionData.ComputedPolicy.NicTeaming.RollingOrder  
       $Obj | Add-Member -Name IsFailoverOrderInherited -MemberType NoteProperty -Value $NicTeamingPolicy.IsFailoverOrderInherited  
   
       $ActiveNics = $Group.ExtensionData.ComputedPolicy.NicTeaming.NicOrder.ActiveNic -join ", "  
         $Obj | Add-Member -Name ActiveNics -MemberType NoteProperty -Value $ActiveNics  
       $StandbyNics = $Group.ExtensionData.ComputedPolicy.NicTeaming.NicOrder.StandbyNics -join ", "  
         $Obj | Add-Member -Name StandbyNics -MemberType NoteProperty -Value $StandbyNics  
       $UnusedNics = $NicTeamingPolicy.UnusedNic -join ", "  
         $Obj | Add-Member -Name UnusedNics -MemberType NoteProperty -Value $UnusedNics  
       
       #All VMs having assigned PortGroup  
       $IPv4Address = $null  
       if ($Portgrouptype -eq "VirtualMachine") {  
         $VMList = $null  
         $VMList = $Group | Get-VM  
         $VMs = $null  
         $VMs = $($VMList | Select-Object -ExpandProperty Name) -join ", "  
         $IPlist = $VMList.guest.Nics | Where-Object {$_.NetworkName -eq $Group.Name}  
         $IPv4List = $IPlist.IpAddress | Where-Object {$_ -match $IPregex}  
         $IPv4Address = $IPv4List -Join ", "  
         $IPv4SubnetMask = $null  
         $PortBindingCompliance = $null  
         $MTU = $null  
         $VmkernelNic = $null  
         $PathStatus = $null  
         $MGMT = $null  
         $vMotion = $null  
         $FT = $null  
         $vSAN = $null  
           
       } #if ($Portgrouptype -eq "VirtualMachine")  
       else {  
         $iSCSIPortGroup = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name).PortGroup | Where-Object {$_ -eq $Group.Name}  
         $VmkernelNicinfo = $VMkernelPorts | Where-Object {$_.PortGroupName -eq $Group.Name}  
         if ($iSCSIPortGroup -ne $null) {  
           $VMList = $null  
           $VMs = $null  
           $PortBinding = "Configured"  
           $IPv4Address = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty IPv4  
           $IPv4SubnetMask = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty IPv4SubnetMask  
           $PortBindingCompliance = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty CompliantStatus  
           $MTU = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty MTU  
           $VmkernelNic = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty Vmknic  
           $PathStatus = $esxcli.iscsi.networkportal.list($iSCSIHBA.Name) | Where-Object {$_.PortGroup -eq $iSCSIPortGroup} | Select-Object -ExpandProperty PathStatus  
           $MGMT = $VmkernelNicinfo.ManagementTrafficEnabled  
           $vMotion = $VmkernelNicinfo.vMotionEnabled  
           $FT = $VmkernelNicinfo.FaultToleranceLoggingEnabled  
           $vSAN = $VmkernelNicinfo.VsanTrafficEnabled  
         } #if ($iSCSIPortGroup -ne $null)  
         else {  
           $VMList = $null  
           $VMs = $null  
           $IPv4Address = $VmkernelNicinfo.IP  
           $IPv4SubnetMask = $VmkernelNicinfo.SubnetMask  
           $PortBindingCompliance = "Not Configured"  
           $MTU = $VmkernelNicinfo.Mtu  
           $VmkernelNic = $VmkernelNicinfo.Name  
           $PathStatus = $null  
           $MGMT = $VmkernelNicinfo.ManagementTrafficEnabled  
           $vMotion = $VmkernelNicinfo.vMotionEnabled  
           $FT = $VmkernelNicinfo.FaultToleranceLoggingEnabled  
           $vSAN = $VmkernelNicinfo.VsanTrafficEnabled  
         } #else #if ($iSCSIPortGroup -ne $null)  
       } #if ($Portgrouptype -eq "VirtualMachine")  
       $Obj | Add-Member -Name VMCount -MemberType NoteProperty -Value $VMList.count  
       $Obj | Add-Member -Name VMs -MemberType NoteProperty -Value $VMs  
       $Obj | Add-Member -Name IPv4Address -MemberType NoteProperty -Value $IPv4Address  
       $Obj | Add-Member -Name IPv4SubnetMask -MemberType NoteProperty -Value $IPv4SubnetMask  
       $Obj | Add-Member -Name PortBindingCompliance -MemberType NoteProperty -Value $PortBindingCompliance  
       $Obj | Add-Member -Name MTU -MemberType NoteProperty -Value $MTU  
       $Obj | Add-Member -Name VmkernelNic -MemberType NoteProperty -Value $VmkernelNic  
       $Obj | Add-Member -Name PathStatus -MemberType NoteProperty $PathStatus  
       $Obj | Add-Member -Name MGMT-Enabled -MemberType NoteProperty $MGMT  
       $Obj | Add-Member -Name vMotion-Enabled -MemberType NoteProperty $vMotion  
       $Obj | Add-Member -Name FT-Enabled -MemberType NoteProperty $vMotion  
       $Obj | Add-Member -Name vSAN-Enabled -MemberType NoteProperty $vSan  
       $report += $obj  
       #check under $NicTeamingPolicy more settings   
     } #foreach ($Group in $PortGroup)  
   } #foreach ($esxi in $VMHosts)  
 } #Process  
 End {  
   $report #| Export-Csv C:\Temp\NetworkInfo.csv -NoTypeInformation  
 } #End

This is how I connected to vcenter server and executed ps1 file. and exported results to csv file, if you don't export information to csv you can view results on csv.

And exported excel/csv file looks like this

Any suggestions and modifications are welcomed.

WSUS on Site Server - Warning SCCM 2012 r2 prerequisite resolved

noreply@blogger.com (kunal) — Wed, 23 Dec 2015 00:36:00 +0530

After resolving all the error and warning, this will be my last prerequisite, (warning) I am going to fulfill for SCCM 2012 R2 installation. although it is not necessary to resolve this warning right now in lab server, but as a best practice I will performing this step and also this will be documented myself and for others if anyone requires help.
Final warning is WSUS on Site Server.

To resolved this I have downloaded and installed WSUS administration console.
Download website.
https://www.microsoft.com/en-us/download/details.aspx?id=5216

Microsoft has written very good document on installing the console.
https://technet.microsoft.com/en-us/library/cc720498%28v=ws.10%29.aspx

I have downloaded tool and running command (As an Administrator) "WSUS30-KB972455-x64.exe CONSOLE_INSTALL=1", It will popup installation windows then select Administration Console Only, and click next until finish.
After this check I installed another Fixes KB2720211 and KB2734608 to clear warning completely.

Last Warnings Resolved
Resolved SCCM (extadsh) Schema Extension Error code 8224 and 8202
Resolved SCCM 2012 R2 - BITs Installed/Enabled Warning & Microsoft Remote Differential Compression (RDC) library failed
SQL Server security mode Warning and SQL Server process memory allocation Warning - SCCM 2012 R2 - Resolved
SCCM 2012 R2 Prerequisite failed (USMT, Deployment Tools, Windows PE) resolved
Resolved SCCM 2012 R2 - Site server computer account administrative rights failed

WSUS on Site Server - Warning SCCM 2012 r2 prerequisite resolved

SCCM 2012 R2 Prerequisite failed (USMT, Deployment Tools, Windows PE) resolved

noreply@blogger.com (kunal) — Tue, 22 Dec 2015 23:54:00 +0530

This is my another article in the SCCM 2012 R2 installation resolving dependencies Prerequisite, I almost resolved all the prerequisite, now few are remaining, Below are the list of Prerequisite can be solve in one shot by installing ADK tool (Windows Assessment and Deployment Kit)

User State Migration Tool (USMT) installed - Failed
Windows Deployment Tools installed -Failed
Windows Preinstallation Environment installaed - Failed

Download ADK tool (Windows Assessment and Deployment Kit) from Microsoft website, and Install it on SCCM, You will require internet to download and install these tools and updates it is around 3.1 GB of data.
Link to download ADK tool
https://www.microsoft.com/en-in/download/details.aspx?id=39982

Once installation done and after running Run check, I have only one warning left to resolve, WSUS on site Server, Which I will be resolving it in next post.

Check out My earlier resolved dependencies
Resolved SCCM (extadsh) Schema Extension Error code 8224 and 8202
Resolved SCCM 2012 R2 - BITs Installed/Enabled Warning & Microsoft Remote Differential Compression (RDC) library failed
SQL Server security mode Warning and SQL Server process memory allocation Warning - SCCM 2012 R2 - Resolved
SCCM 2012 R2 Prerequisite failed (USMT, Deployment Tools, Windows PE) resolved
Resolved SCCM 2012 R2 - Site server computer account administrative rights failed

WSUS on Site Server - Warning SCCM 2012 r2 prerequisite resolved

PowerCli - The remote server returned an error: (407) Proxy Authentication Required

noreply@blogger.com (kunal) — Mon, 21 Dec 2015 22:35:00 +0530

Today one of my colleague had below issue while accessing Powercli, He was able to connect to vcenter, but after executing any command he was getting Proxy Authentication. 2 months back I had faced same issue Connect-VIserver Could not connect using the requested protocol. and same solution apply to this problem.
################################################################################
Get-VM : 12/21/2015 7:04:05 PM    Get-VM        The remote server returned an error: (407) Proxy Authentication
Required.
At line:1 char:1
+ Get-VM
+ ~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Get-VM], ViError
    + FullyQualifiedErrorId : Client20_QueryServiceImpl_RetrievePropertiesEx_ViError,VMware.VimAutomation.ViCore.Cmdle
   ts.Commands.GetVM
################################################################################

This is how I troubleshooted issue.

I executed command Get-VM,
But received error -The remote server returned an error: (407) Proxy Authentication
I checked my status whether i am connected to vcenter using $Global:DefaultVIServer.
It was connected, Name is the IP address of my vCenter.
Next I checked Get-PowerCLIConfiguration
I found ProxyPolicy is set to UseSystemProxy for Session scope. and it is using my proxy to connect to vCenter.
I change the proxy policy to NoProxy for Session Scope using Set-PowerCLIConfiguration -Scope Session -ProxyPolicy NoProxy
Press Y to confirmation on changing settings
Once the changes done, You will see changed result.
This is the last one, I checked Get-VM and without any issue I got my results on the console.

SQL Server security mode Warning and SQL Server process memory allocation Warning - SCCM 2012 R2 - Resolved

noreply@blogger.com (kunal) — Mon, 21 Dec 2015 00:37:00 +0530

I received 2 SQL server related warning while installing SCCM. one of the warning is SQL Server security mode warning - The SQL Server name specified is configured for SQL authentication security. It is recommended to configure the SQL Server to operate only in Windows authentication security before you continue Configuration Manager Setup.
To resolve this warning you will have to change SQL server configuration.

On the SQL Server, Right click SQL instance go to properties and then Security. Make sure you have selected Windows Authentication Mode only, and run check to verify warning is gone.

And the second Warning is SQL Server process memory allocation - Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see http://go.microsoft.com/fwlink/p/?LinkId=233759.

Other Errors Resolved

Resolved SCCM (extadsh) Schema Extension Error code 8224 and 8202
Resolved SCCM 2012 R2 - BITs Installed/Enabled Warning & Microsoft Remote Differential Compression (RDC) library failed
SQL Server security mode Warning and SQL Server process memory allocation Warning - SCCM 2012 R2 - Resolved
SCCM 2012 R2 Prerequisite failed (USMT, Deployment Tools, Windows PE) resolved
Resolved SCCM 2012 R2 - Site server computer account administrative rights failed

WSUS on Site Server - Warning SCCM 2012 r2 prerequisite resolved

On Same properties of sql server, under Memory set minimum and maximum memory to 8192. and warning will go away.

I am clearing warnings and errors one by one, next article I will be resolving WSUS on site Server Warning.

vGeek

Compare Different Laptops for Home Lab

Stellar Data Recovery Technician Review

Cisco CCNA Lab Guide - Wants to be master of CISCO networks?

PART 4.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY

Blog | vGeek - Tales from real IT system Administration environment

Top vBlog 2016 - Time to Choose the Top Blogs.

Last year I registered my blog for top vblog, Again Top vBlog 2016 voting on vSphere-Land has been opened . Please vote me for keep bloggers motivated.

Find CDP or LLDP information on Windows Servers

Error resolved: Hyperv cannot be installed: A Hyperviser is already running.

Powershell Rocks - Creating virtual Nic cards for testing (Standalone HyperV)

Resolved: The trust relationship between this workstation and the primary domain failed

Install missing Powershell ISE on Windows Server 2008 R2

vSphere Datastores inventory report powercli - Volume 2

import vCenter roles (privileges) - Powercli.

this is screenshot from my previous post it contains all the roles. Here is the script. I hope I am keeping all simple.

Export vcenter roles (privileges) - Powercli.

Change username/password configured on logon tab of Windows Service - Powershell

List account configured on logon of Windows Service - Powershell

Importing VM annotation (Attributes) and notes from CSV file into vCenter - Powercli

Exporting virtual machine annotation (Attributes) and notes to CSV file - Powercli

Move/Migrate VMs to folder Path on another vCenter - Powercli

Other Useful blogs

Get vCenter VM folder Path from VMs and Templates- Powercli

Other Useful blogs

Save complete virtual PortGroup information Settings - Powercli

WSUS on Site Server - Warning SCCM 2012 r2 prerequisite resolved

SCCM 2012 R2 Prerequisite failed (USMT, Deployment Tools, Windows PE) resolved

PowerCli - The remote server returned an error: (407) Proxy Authentication Required

SQL Server security mode Warning and SQL Server process memory allocation Warning - SCCM 2012 R2 - Resolved

this is screenshot from my previous post it contains all the roles.

Here is the script. I hope I am keeping all simple.