Tag Info

New answers tagged

0

I believe the salt.states.rvm docs are missing the state which actually installs rvm: install_rvm: cmd.run: - name: curl -sSL https://get.rvm.io | bash - user: rvm - unless: /home/rvm/.rvm/bin/rvm --version


2

It is a bug in WDS. When you approve a UEFI device it gives the wrong permissions. If you look under the security permissions on the computer object you will see it has set deny for Domain Admins against the 'Change password' and 'Reset password'. Remove the deny for both of these and you are good to go. You will need to do this for each UEFI computer you ...


2

The point of keeping secrets out of source code is so they don't go into source control. This is particularly useful in open source projects. When deployed, it doesn't matter if the secret's in a file or envvar. What's important is that only the OS user that your program is running as can read it. This is the default for envvars, which is convenient. Root ...


0

It seems problem is a combination of old hardware and possible not provides network drivers. At least that is my guess. We recieved the new hard ware and now the deployment process continues past this point. (How ever it now hangs at the end. Can not join the domain.) In case you wonder. The new hardware is: Server ASRock J1900D2Y, 16 GB, 3TB HDD ...


-1

use MDT with a database for inventory (if required) you don't need a separate script or contract for various drivers or applications, you can use the hardware model identification built right into windows to determine the proper drivers and or system level apps. You don't install ANY drivers in the image using this model- simply add the drivers to the ...


1

May be helpful for someone: Check, that you have NO such dependencies in your pom.xml: <dependency> <groupId>org.apache.tomcat.maven</groupId> <artifactId>tomcat7-maven-plugin</artifactId> <version>2.2</version> </dependency> <dependency> ...


0

I think that different DHCP servers can work on the same physical network under certain configurations. There are two ways to do that If you have a computer with ONLY one network-port, You'll have to: Install VM first; Fix the IP address of your VM into a DIFFERENT SUBNET than your original network; Install Tftp32 on this VM  Make Tftp32  DHCP ...


1

Your scenario is exactly what customsettings.ini in MDT is designed to address. You can create deployment share rules in MDT that automatically pick a task sequence and/or driver profile during deployment. This is done via identifiers like the computer model or MAC address. See Configure MDT Deployment Share Rules. I’d really suggest reading over the ...



Top 50 recent answers are included