How do I install from url using choco_installed_packages in default.config.yml? about windows-playbook HOT 9 CLOSED

Hey Simbaclaws,

Thank you for being so interested in this playbook.
Implementing this functionality with the ansible.windows.win_package module should be relatively easy.
I believe the example below represents the functionality you are asking for. Of course, it has to be adjusted to be more dynamic.

- name: Install Remote Desktop Connection Manager from msi with a permanent log
  ansible.windows.win_package:
    path: https://download.microsoft.com/download/A/F/0/AF0071F3-B198-4A35-AA90-C68D103BDCCF/rdcman.msi
    product_id: '{0240359E-6A4C-4884-9E94-B397A02D893C}'
    state: present
    log_path: D:\logs\vcredist_x64-exe-{{lookup('pipe', 'date +%Y%m%dT%H%M%S')}}.log

If this functionality is urgent for you - feel free to contribute, as I likely won't have time to work on this in the next couple of weeks.

from windows-playbook.

Hi Alex,

I forked your repo for my personal setup of my gaming pc.
Does the ansible.windows.win_package only work for windows packages from microsoft or can I use a dynamic url from some other source on the web? And is it required to specify a product_id?

I won't need any of this urgently, and if I did, I'd use it on my own forked repo because I'd have my own personal setup...
Thank you so much for making this playbook, it's probably going to help me save some time.

from windows-playbook.

@Simbaclaws ansible.windows.win_package can be used with any supported packages (.exe, .msi, .msp, .appx, .appxbundle, .msix, and .msixbundle.) from any vendor. You can find full module documentation here.
Out of curiosity what software installation do you wan to automate?

from windows-playbook.

Mostly my current setup for a develper + gaming machine, I've already created a huge list of software to install with chocolatey.

You can see my adjusted default.config.yml in my fork of your repo. I already pushed it.

For the win_package, I was thinking about some software that I have to manually download, specifically Chitubox for 3d printing since it isn't in the chocolatey repo.

from windows-playbook.

Sorry but I have another question, is there a way to run the playbook on my local windows machine by fetching it from the repository letting it provision itself somehow? Instead of having a workstation that provisions it through an ip address?

from windows-playbook.

@Simbaclaws, you can do this from within the WSL2 Linux machine. Here is a tutorial that you can use to configure your windows machine.
Unfortunately, you cannot install ansible directly to a windows machine as you usually do on Linux or MacOS.

from windows-playbook.

So there is no ansible-pull command I could use for within powershell for example? I'm looking to create a ansible-pull command that basically pulls a ansible playbook and configures the local machine by inserting a single command... I'll do some research to see if this is at all available in windows somehow, thank you for your time. Otherwise I'll have to setup a central pushing station that pushes the configuration onto the machines I'm trying to install... Doing it from WSL might be an option, but I'd need a script that basically installs WSL and runs the commands in that case.

There might be some downsides to pushing, mainly that I have some machines in virtual lans and they would have to communicate with one another somehow with inter vlan communication.

EDIT: This might seem helpful: https://stackoverflow.com/questions/58345011/setup-windows-10-workstation-using-ansible-installed-on-wsl

EDIT2: This repository might be helpful for me: https://github.com/gmarokov/ansible-playbook-postinstall-win

from windows-playbook.

I just automated the installation of the windows features and wsl as well as runnning, cloning etc the playbook automatically so you simply have 1 single command that provisions a windows pc from itself. The script basically asks for your local admin username and password at some point, and does now all of the installation for you.

You might want to checkout my repository fork on this :)

This does mean I had to remove all the reboots from the yml's... Because it runs locally now and not from another machine.

This should work for a clean windows install... I'm testing that soon.

I also have to do some cleanup afterwards.

from windows-playbook.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from windows-playbook.