
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-01-2019 11:33 AM
On each version update of Windows we face a similar challenge
We created a command to install the .NET 3.5 in Windows 10 v 1906.
On Windows v1809 this was still working.
However on v1906 the deployment fails due to lack of elevated permissions.
We always install with Scanning Credentials as this account is also local admin on all assets however
it seems DISM requires the NAME administrator for these elevated permissions.
The default account ADMINISTRATOR however is disabled by global company policy.
So if I run the above from a CMD box that was "run as administrator" it's working fine.
My question is: How can I run the same command from the Deployment screen in LANsweeper with these elevated permissions?
Kind regards

We created a command to install the .NET 3.5 in Windows 10 v 1906.
dism /online /loglevel:4 /Add-Package /PackagePath:"\...\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab" /NoRestart
On Windows v1809 this was still working.
However on v1906 the deployment fails due to lack of elevated permissions.
We always install with Scanning Credentials as this account is also local admin on all assets however
it seems DISM requires the NAME administrator for these elevated permissions.
The default account ADMINISTRATOR however is disabled by global company policy.
So if I run the above from a CMD box that was "run as administrator" it's working fine.
My question is: How can I run the same command from the Deployment screen in LANsweeper with these elevated permissions?
Kind regards
Labels:
- Labels:
-
General Discussion
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-15-2019 04:49 PM
Just curious how were you able to get this to script to install the complete 3.5 .net framework on a Win10, without any error messages.... error: 0x800F0906, 0x800F081F, 0x800F0907...
Using this script...
dism /online /loglevel:4 /Add-Package /PackagePath:"\...\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab" /NoRestart
Im running into errors listed above running it in PowerShell and CMD elevated...
Thank you..TCI
Using this script...
dism /online /loglevel:4 /Add-Package /PackagePath:"\...\microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab" /NoRestart
Im running into errors listed above running it in PowerShell and CMD elevated...
Thank you..TCI

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-12-2019 09:51 AM
System account might indeed work.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-10-2019 04:22 PM
Have you tried just running as system account? Thats what i run most of our deployments on since its basically god mode on computer.
