More Basic Guidance

[Flyslinger2]

I know PowerShell reasonably well. I know the IA process reasonably well. I need to automate a new environment that I inherited for STIGs. I'd much prefer to do it through PS.

I've spent the biggest part of a day reading through this and I'm more lost now than when I was BEFORE reading this.

My environment is totally air-gapped. I have to d/l everything to an internet facing computer and then sneaker net via encrypted disc to the other network.

I downloaded PowerSTIG and all of it's dependencies manually. I didn't see a list detailing if the dependencies had to be imported in a particular order. Last module I import is PowerSTIG itself. It gives me an error that a dependency (ComputerManagmentDSC) is missing.

$env:psmodulepath gives:

1. C:\Program Files\WindowsPowerShell\Modules - everything gets installed here.
2. c:\users<UserName>\documents\windowspowershell\modules - doesnt physically exist.
3. C:\Windows\System32\WindowsPowerShell\v1.0\Modules - nothing gets installed here.

I can't get beyond the install.

[Flyslinger2]

Today I built a Win10 VM in Oracle VB and set up a local Repository and deleted PSGallery from the search options.

I downloaded the same modules that I used on my disconnected networks with all the lovely security stuff installed. My local VM has none of these additional security enhancements installed nor is it domain joined like my servers are on the disconnected networks. I manually installed all of the dependancies first and then attempted to install PowerSTIG. I get the same error. Screen shot attached.

[bcwilhite]

@Flyslinger2 - When you manually downloaded the modules that PowerSTIG requires, did you by chance download the exact version numbers listed in the manifest file?

[Flyslinger2]

Yes. My findings are during the manual installation some modules do not get installed in the properly named folder: 2.12.0 for PSDscResources instead of 2.12.0.0 When you issue the command import-module PowerSTIG it will error out on the sub-Module that got install incorrectly. Manually navigate to that folder C:\Program Files\WindowsPowerShell\Modules<Module Name> and correct the sub-folder name based on the version number of the file. I found that all incorrectly installed modules were missing .0 on the version subfolder.