I created a windows image (sysprep), with optional contents inside.
This optional content I would like to install on other machines that don't have it.
I mount the .wim image on the machine:
dism /Online /Add-capability /capabilityName:SNMP.Client~~~~0.0.1.0 /Source:c:\ISO\
Why does DISM have to make online requests if I tell it to fetch what I'm requesting via the Source command?
Having a domain with blocked update policies. How can I fix this?
Thank's
If I enable traffic to microsoft, without blocking policies, the installation proceeds without problems...
At this point I wonder, what is the use of mounting the .wim image if it has to make online requests to install the package I need (which is present in the .wim image. ???
Related
If not mistaken,the error occured after I misclick a notification of a antivirus software that request for a permission.My computer is using Windows 10.May I know how to solve this problem?
Older answers on this software installation:
Node.js - Cannot Install it is showing an error because of .msi
Node.js install fails on Windows 10 1803
Blocking: This sort of problem can definitely be caused by an anti-virus software blocking access to the MSI in question. Disable the anti-virus temporarily and try again. If unable to do so, perhaps try to install on a virtual machine? (for testing or real use).
Windows Installer: Just to get it out of the way: I see some recommendations to re-register the Windows Installer components, but I prefer to eliminate other causes first (a broken Windows Installer usually indicates more serious system-wide problems - such as malware infection, or full disk or something else very fundamental).
Virustotal.com: Before temporarily disabling your anti-virus (the procedure for this is obviously different for each vendor), you should verify the actual binary or MSI using the virus checker interactively and also upload the file to https://www.virustotal.com/ to make sure the MSI isn't actually infected - if it is your anti-virus is doing its job.
Re-Download: It is also a good idea to re-download the MSI from the vendor site in case it has gotten corrupted during download. This happens very frequently. I have seen days wasted with corrupted installation media the unexpected cause. Virus test this new download too using https://www.virustotal.com/ (you want to check both old and new binary for malware - the file available for download can be infected).
Other Causes: There are a number of other causes that are common for failing installers. I have several older answers on this, but maybe this is the easier one to browse: Common causes of failed installations (setup.exe or mysetup.msi fail to install). Here is a quick extract (please do visit the link):
The most common issues seem to be: security software interference, malware infected machine, corrupted download, missing runtimes, out of disk space, blocking mechanisms on the machine from corporate policies, etc...
Other Links:
WiX, deployment and setup links
I cannot reinstall node.js on windows 10
I think your problem is not from the node.js but from the Windows installer itself.
I solved mine by following the instruction here (from the Microsoft forum).
Method 1:
Perform System File Check (SFC), and then check if this fixes the issue.
Follow the steps:
a. Press “Windows Key + Q” to open Charms Bar.
b. Type “cmd” without quotes in the search box.
c. On the left pane, right-click on the “cmd” option and select “Run as Administrator”.
d. Type ‘sfc /scannow’ without quotes and hit enter.
Method 2:
I would also suggest you to run the System update readiness command. It detects incorrect manifests, cabinets or registry data, it may replace the incorrect data with corrected version available. Follow the steps.
4. Press Windows key + X.
5. Click command prompt (run as administrator).
6. In the Administrator: Command Prompt window, type the following commands. Press Enter key after each command:
DISM.exe /Online /Cleanup-image /Scanhealth
DISM.exe /Online /Cleanup-image /Restorehealth
In my case, the first method solved the problem.
Up to today, I have been using a single boot.wim file and a single install.wim file (captured from a configured PC, with DISM) to install Windows 10 from my Server 2012R2 WDS server. Now we have purchased new hardware and I need to add a driver to both .wim files. I was able to use the following steps to put the driver into the boot.wim:
Dism.exe /mount-wim /wimfile:d:\temp\boot.wim /index:2 /mountdir:d:\temp\mount
Dism.exe /image:"d:\temp\mount" /add-driver /driver:"d:\temp\drivers\IntelI354"
Once that was done, I PXE booted and was able to pull down my install image. So, I used the same steps to update install.wim, but when I pulled down the updated image, the NIC was not detected.
I followed the steps in scenario 1, from https://technet.microsoft.com/en-us/library/dd348456%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396, to deploy driver packages through WDS, but it obviously didn't work.
What do I need to do, to get this new NIC driver properly installed in my image?
Thanks.
I ended up using: https://blogs.technet.microsoft.com/doxley/2007/12/13/editing-the-registry-of-your-wim-without-having-to-recapture/ to load the registry file from the WIM, and https://technet.microsoft.com/en-us/library/cc753716(v=ws.11).aspx to add my desired directory to the DevicePath registry entry.
for a remote backup and recovery solution, I want to create a WinPE Environment with embedded Teamviewer (newest possible version)
Now I found a tutorial which describes this steps. (unfortunately its not english so its just for information)
http://www.andysblog.de/windows-teamviewer-und-winpe-eine-boot-cd-fuer-den-remote-support
You have to mount the WIM Image, copy few DLLs into the System32 Folder
c:\windows\system32\avicap32.dll
c:\windows\system32\msvfw32.dll
c:\windows\system32\de-de\avicap32.dll.mui
c:\windows\system32\de-de\msvfw32.dll.mui
and use the Teamviewer Quicksupport Ver. 5 (Portable Version works too)
which is important because all versions above 5 doesn´t work in the WinPE environment.
I did everything as decribed (in a VM machine), and tried to connect over LAN (without ID - not over the Teamviewer server) - My Teamviewer 10 didn´t connect and gave the following error: "Protocol negotiation failed"
Any suggestions?
The second problem is, that I would like to run the newest possible version, according to some reports, Teamviewer above Ver 5 checks in which account it runs. - If it is the SYSTEM account it will try to switch the account, if it fails it closes without any error message.
So I need also a solution for this. Maybe how to run programs in WinPE as different user and not as the default SYSTEM account.
Thanks for any suggestions.
Well, I think I figured it out.
You have to run the full install in WinPE and check the "run-on-startup-feature" which registers it as a service. Now I was able to connect without any problems.
Though it does not have any sense to "install" Teamviewer everytime I boot the WinPE environment, so I did all the settings I need and exported them to a *.reg File on a USB drive.
Also copied the new installed Teamviewer folder to include it in the WIM Image later, and will create a batch file which loads the *.reg File on every boot and then starts up "Teamwiever" - Let´s see if this works.
I'm getting requests from 'the Field' to make my agent deployment 'easier' but I'm at a loss as to how.
Right now, I provide a user Interface to install and configure the agents.
To deploy the agents, I relied on older Windows technologies, here are the steps I use:
Start dependent services via remote SCM
Copy the agent.MSI via the File Administrative shares
Configure the agent's settings via remote registry calls
Use WMI to remotely silently run the agent.msi
Use the Administrative shares to move the agent.msi to the program folder (for uninstalling later)
To allow all these steps to happen, I need:
1. the firewall to configured correctly
2. the 'installing' user has to have admin access to the remote computer
3. Remote File Admin shares have to be turned on.
4. (I turn on WMI and Remote Registry remotely)
This deployment system was built back in the 2003 days.
Is there some better way now? Maybe a deployment library I can use?
thank you.
The best you can do here is to create a properly behaving .MSI that supports silent installation. It is then up to your user communities to plan their own deployments using the tools of their choice such as SCCM. Much more detail is required in order to give exact suggestions.
In VS2010 Beta 2, from the Help Library Manager, after selecting local help, and downloading the VS Documentation, it won't launch.
Here's what I have installed:
Here's what I'm clicking in the Start Menu:
Here's the result:
Ideas?
Thanks,
Adam
I recommend reporting this bug on Microsoft Connect so that the Visual Studio product team can take a look at this.
This seems like a rather specific problem and not a general programming question.
I also had problems with VS 2010 Beta 2 help, or rather with MS Help 3, which is new with 2010 . There is a known issue with the Help Listener Service trying to listen on port 80. MS document a procedure to change this port, and my help was back up after following it. From the the ReadMe_ENG.htm file that is installed with MS Help:
Removal of Help 3.0 will not remove content from user's machine;
they should run HLM to remove content
Product Documentation shortcut will not work after uninstall of Help
3.0
Help Library Manager requires the BITS service to be running if you
want to use the “Check for Updates” or
“Find Content online” features.
Removing content and installing
content locally does not require the
BITS service.
Help Library Manager will hang if you attempt to install offline
content but there is not sufficient
disk space for the BITS service to
download the content
If port 80 is used by another process (not via the http.sys service)
then the Help listener will not be
able to attach and use port 80 and
will fail. The port number can be
changed by adding a string registry
value ListenerPort under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Help3
with the value of the port to use (eg.
81). Due to the http.sys ACL settings
it is necessary to run the following
http.sys configuration command from an
admin elevated command line. On
Vista, Win2k8, and Windows 7 run the
following native command: netsh http
add urlacl url=http://127.0.0.1:/help/ sddl=D:(A;;GX;;;WD)
On Windows Xp, and Win2K3 run the
following command:
httpcfg set urlacl /u
http://127.0.0.1:/help/
/a D:(A;;GX;;;WD)
If the command is not found then it
might be necessary to download the
httpcfg.exe from Microsoft as part of
the Windows XP Service Pack 2 support
Tools
(http://www.microsoft.com/downloads/details.aspx?amp;displaylang=en&familyid=49ae8576-9bb9-4126-9761-ba8011fabf38&displaylang=en).
Now the Microsoft Help Listener will
run on the selected port number.
ADDENDUM:
I also ended up installing MS Help 3 manually, and using the Help->Manage Help Settings menu command. On the VS 2010 installation 'disk', I ran WCU\Help\HelpSetup.exe, after removing help via Add/Remove programs. Note the folder HelpSetup installs to, and then in VS 2010, open the Help Library Manager (Help->Manage Help Settings), then Find Content on Disk, and then supply the location HelpSetup installed to. Help 3 will take it from there.