Lakatta wrote:
This is a good one. Good post.
We wrote a powershell script to do the dirty work for the most part. You will have to change the report location and some variables to where you 32 and 64 bit admin installs are.
Checks for 2016 already installed
Checks 32 or 64 bit architecture
Runs 32 or 64 bit
Rescans computer
We have pre-built dynamic groups, schedules, etc ready to deploy. So when we are given the thumbs up, we check the boxes and pray. It's solid, and be aware sharepoint 2010 easily corrupts and some residual junk doesn't uninstall all the time.
Hope it helps. Rename to .xml and .ps1
ps
It was a quick build due to time frame constraints on another project
Hi,
I do not understand the ps script txt file.
Do the XML files need to be local on every machine?
it's not possible to put them on the lansweeper share and use them from there?
What does the command out-file \\networkshare\$env:computername.txt -append refers to, does it copy something to each computer from a netowork share?
It seems like a good script but I don't understand many parts of it unfortunately and I do know some power shell.
When using the ODT tool, the installation gets stuck sometimes and times out so I was thinking that maybe your script my be a better solution.