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.
Related
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.
I am currently trying to install my vb6 app on a Windows 8.1 computer via TeamViewer (it's kind of like remote desktop). However, the installation always hangs up after all the files are copied and this message is displayed:
Setup is updating your system
We've tried it on our own Win8.1Pro desktop (via Remote Desktop this time) and Win2008Server(both via Remote Desktop), and it installed just fine.
Right now, we've narrowed it down to one culprit - MyProjectInfo.exe the actual ActiveX .exe. Whether it is me trying to run the .exe for the first time to register it to DCOMCNFG or whether it is the setup.exe running the script $(EXESelfRegister) it just freezes up.
What differences should i look for between 1) our win8.1Pro and win2008server and 2) their win8.1? If it some coding/reference/dependency issue, what could be the cause for why it doesn't error in our desktops?
Thank you for all the help.
Uhmm... this is getting embarrassing.
Avast (present in the other person's Win8.1) was blocking MyProjectInfo.exe from running (which is basically what is does with $(EXESelfRegister).
To properly proceed with registering my ActiveEXE program, I had to turn Avast off for a while. And that was that.
This problem may also occur with other anti-virus scanners as well.
We've successfully set-up WDS (Windows Deployment Services) and had it all working (it's serving an unattended Windows 7 x64 installation, the user only has to F12 then wait for the install to finish) but it no longer works the way it did before.
We're trying to F12 the exact same machine where it used to work. The WDS part of the installation is still automatic (unattended) but ImageUnattend.xml does not seem to run on the client at all now, it gets stuck at the language selection (everything after that is manual as well which is supposed to be automatic).
Inspecting C:\windows\panther on the client machine shows that WDS pops up with an error: WDS CallBack_WdsClient_CopyPrivatesDone: Failed to process client unattend variables.
Changing "%MACHINENAME%" to "*" in the ImageUnattend.xml file makes it all automatic again, however it then renames the computer incorrectly.
The variable %MACHINENAME% worked before, so why does it not work now? Has anyone else met this issue before?
Using a different user (domain administrator) in the ImageUnattend.xml file does not seem to change anything.
After countless of attempts with at least 15 new ImageUnattend.xml files, I decided to restart the server and use the original files I knew worked before.
This fixed it.
I am trying to create a dev box for SharePoint 2010 Server utilizing the following:
http://blogs.msdn.com/b/cjohnson/archive/2010/10/28/announcing-sharepoint-easy-setup-for-developers.aspx
So first of all this is new to me. I understand that these are instructions are for dual boot in Windows Native, but I am more interested in using a VHD/image of the OS to run on VMWare.
I have tried creating an image of a running virtual machine with sysprep tool, but hit a dead end with capturing the image to a file that I can reference within the running machine to run the scripts against.
I took a look at Diskpart on TechNet, but as I am new to this, I am not sure this is what I want to do?
I tried installing to the local host (virtual machine that is running) and am getting an error there also; fails at Windows Identity Framework.
It is a clean install of Windows 7 (literally nothing else), and the UAC has been disabled.
Is there any insite, help, or advice anyone can provide me regarding this? I would really appreciate it as I have to get working on the development aspects of SP (workflows, web parts,etc), and need a dev env, and I can't seem to get anywhere with this.
Thanks
Justin
I have Informix version 11.50 installed on my Windows machine. According to this link, in order to start the server, it should be done through Windows services, look for Informix IDS - instance_name. It is supposed to start when Windows is started up, but for my case it is not, and it wasn't started. Thus I start it up manually by double clicking on it, and it prompt me an error:
The service did not respond to the start or control request in a
timely fashion.
May I know is there any solution in order to start up the local Informix DB on windows?
You will have to check what went wrong in Informix log. It is located in Informix dir and has server name with .log extension (for example c:\informix\ol_test.log). In this file there is information about running server like:
12:42:36 IBM Informix Dynamic Server Started.
Check this file and give us more details if you will not know how to solve reported problems.
Installation of Informix in Windows Vista has been failed. Due to the reason this Informix thing is not able to uninstall and not even allow me to configure a database. Even though I have manually delete the whole folder from Program Files, when trying to install a new copy of Informix, it prompt me the "Invalid ISV name" thing which I totally running out of clue with.
I found a post mention that Vista is not a good platform for Informix. Forget about Windows as a Server a.k.a. WAAS.
xD