Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to asbuild report #125

Open
3 tasks done
kedargodabole opened this issue Oct 30, 2024 · 2 comments
Open
3 tasks done

unable to asbuild report #125

kedargodabole opened this issue Oct 30, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@kedargodabole
Copy link

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

@kedargodabole kedargodabole added the bug Something isn't working label Oct 30, 2024
@tpcarman
Copy link
Contributor

Have you followed the offline installation instructions correctly?

@kedargodabole
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants