search

AsBuiltReport / AsBuiltReport.VMware.vSphere

Repository for AsBuiltReport VMware vSphere module
https://www.asbuiltreport.com
MIT License
114 stars 39 forks source link

unable to asbuild report #125

Open kedargodabole opened 3 weeks ago

kedargodabole commented 3 weeks ago

Bug description

i am running as build report from windows server and my server doesnt have internet. Hence i manually downloaded latest powercli and asbuildreport.vmware.vsphere module and pasted the files in c:\windows\system32\windowspowershell\1.0\modules folder. then i run the command to create json file :New-AsBuiltReportConfig -Report 'VMware.vSphere' -Folderpath 'C:\TEMP' -Force and getting below error. not sure what i am missing. I am not good at PS scripting just trying the script. New-AsBuiltReportConfig : The term 'New-AsBuiltReportConfig' is not recognized as the name of a cmdlet, function, script file,

Command-line input

New-AsBuiltReportConfig -Report 'VMware.vSphere' -Folderpath 'C:\TEMP' -Force

Steps to reproduce

explained above

Expected behaviour

NA

Screenshots

No response

Operating System

windows server 2016

PowerShell Version

5.1.14393.7426

PowerShell Modules

asbuildreport.vmware.vsphere

Additional Context

No response

Before submitting

tpcarman commented 3 weeks ago

Have you followed the offline installation instructions correctly?

kedargodabole commented 3 weeks ago

yes.. thanks for suggestion. HTML and word documents are getting generated but it has minimal information and script throwing this error. I dont see any issues when i use connectvi-server 'VC-name' Get-PatchBaseline : 1/11/2024 1:07:45 AM Get-PatchBaseline There was no endpoint listening at https://XXXXXXXXXXX/vci/sdk that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.