1 2 Previous Next 16 Replies Latest reply on Feb 27, 2019 8:27 AM by MCioe Go to original post
      • 15. Re: PowerCLI very slow to load on a Windows 2012R2 Server
        andrea1975 Novice

        Hi LucD,

        I've found a workaround:

        when I run the Import-PSSnapin I noticed (with wireshark) a lot of failed traffic to WAN addresses, so, I've set, into Internet Options a fake proxy ( excluding from the proxy my active directory domain's DNS name (so I can connect to the virtual center bypassing the fake proxy)

        This is now the execution time:


        Windows PowerShell

        Copyright (C) 2013 Microsoft Corporation. All rights reserved.



        PS C:\Users\MyUser> Measure-Command {Add-PSSnapin vmware.vimautomation.core}



        Days              : 0

        Hours             : 0

        Minutes           : 0

        Seconds           : 2

        Milliseconds      : 774

        Ticks             : 27745259

        TotalDays         : 3.2112568287037E-05

        TotalHours        : 0.000770701638888889

        TotalMinutes      : 0.0462420983333333

        TotalSeconds      : 2.7745259

        TotalMilliseconds : 2774.5259


        Not bad! Execution time lowered from 16 sec to 2.8 sec

        • 16. Re: PowerCLI very slow to load on a Windows 2012R2 Server
          MCioe Enthusiast

          I found I had a similar timing  issue with PowerCLI 11 on Windows 2012R2 in a vSphere 6.5 environment - also off-line.


          The thing that worked for me was to delete all the default Root Hints in my DNS and the performance improved dramatically.


          Apparently, when you stand up a DNS server, roughly 15 Root Hint entries are automatically added.  These IP addresses have no connectivity to the real world, but the Import-module cmdlet will wait for a network timeout looking for CRLs for each of these IP entries before returning to the command line. It would take about 3 minutes to complete.


          I also have been told that unless you delete the root hints from 3 locations in your environment (I believe they are also in some registry keys), then these hints will come back in the DNS and you have to delete them again.



          1 2 Previous Next