-
- Novice
- Posts: 4
- Liked: 2 times
- Joined: Jul 21, 2015 7:26 pm
- Full Name: Neil Bird
- Contact:
Feature Request: Built with custom WIM
I am sorry if this has been suggested or dealt with, I searched and found nothing relevant.
Although I appreciate that the Recovery media is built using the "RE", and there are options to build within VEB when the RE is unavailable, I was hoping for one of two things.
I would be happy to either
1. have VEB possibly mount, inject and add components into an existing custom WIM
2. Have access to the VEB script/components to do so myself.
If I am allowed to send props to another community, I use Winbuilder for custom tools.
I certainly appreciate that Veeam has created a fantastic tool, however I am not sure if what I want is just because I like to tinker, or that it would in fact be helpful to others.
I know that there is a thread here to "multi-boot" iso's on one media. I currently extract WIM's and multi-boot them through WB for ease, and it works brilliantly to save space. However, my need is a little more complex. I wish to send a "kit" to remote offices, and currently the best method to do a remote diag/restore is through a custom WIM that I was able to add a "previous product" to, (has VNC server built in). Thus a single wim would be best, and saves bandwidth if I need to push a new smaller.iso to a remote site.
Happy to work on a WB plugin if Veeam is ok with this.
... or I would be happy to put in a different feature request to allow injecting a VNC server or similar along with other selected tools....
Although I appreciate that the Recovery media is built using the "RE", and there are options to build within VEB when the RE is unavailable, I was hoping for one of two things.
I would be happy to either
1. have VEB possibly mount, inject and add components into an existing custom WIM
2. Have access to the VEB script/components to do so myself.
If I am allowed to send props to another community, I use Winbuilder for custom tools.
I certainly appreciate that Veeam has created a fantastic tool, however I am not sure if what I want is just because I like to tinker, or that it would in fact be helpful to others.
I know that there is a thread here to "multi-boot" iso's on one media. I currently extract WIM's and multi-boot them through WB for ease, and it works brilliantly to save space. However, my need is a little more complex. I wish to send a "kit" to remote offices, and currently the best method to do a remote diag/restore is through a custom WIM that I was able to add a "previous product" to, (has VNC server built in). Thus a single wim would be best, and saves bandwidth if I need to push a new smaller.iso to a remote site.
Happy to work on a WB plugin if Veeam is ok with this.
... or I would be happy to put in a different feature request to allow injecting a VNC server or similar along with other selected tools....
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Feature Request: Built with custom WIM
Hello Neil,
Thank you for sharing your thoughts and I sorry for taking so long to get back to you.
Thank you for sharing your thoughts and I sorry for taking so long to get back to you.
You could try to manually extract the data from a recovery media ISO and load it in the customer WIM, might work.have VEB possibly mount, inject and add components into an existing custom WIM
No scripts for Recovery media creation available - we do that via UI onlyHave access to the VEB script/components to do so myself.
Is ok and you are welcomeHappy to work on a WB plugin if Veeam is ok with this.
-
- Novice
- Posts: 4
- Liked: 2 times
- Joined: Jul 21, 2015 7:26 pm
- Full Name: Neil Bird
- Contact:
Re: Feature Request: Built with custom WIM
Super!
I will continue to look at this and will report back if anyone else is interested.
regards,
I will continue to look at this and will report back if anyone else is interested.
regards,
-
- Novice
- Posts: 4
- Liked: 2 times
- Joined: Jul 21, 2015 7:26 pm
- Full Name: Neil Bird
- Contact:
Re: Feature Request: Built with custom WIM
Just in case anyone was interested in using Winbuilder, I have a very basic script that has allowed the inclusion of the recovery components by copying from an installed version of Endpoint.
I have only tested it on a Win10PE x64 build, however the script accounts for the reg entries for .net 4 on both x86 and x64
.net is not copied in this script, and I am using a script within the project for the .net 4 as required. (have included the registry entries in the event you wish to mod the script to copy the .net files yourself)
.net found in "Windows\Microsoft.net" however only a portion of the folder is required
save the code below as a .script file and place in the apps folder of your winbuilder project. I am sure it can be cleaner... but it gets the job done.
created from the file list and .reg files found within the installed application.
It appears that the same files are able to be used in all x86 and x64 builds, as I did a file comparison, but again, not tested.
Of course, you can just use the already great Veeam boot.wim, I just wanted to see if it could be done. To benefit from the Veeam built wim image, just take the boot.wim and include it in a multi-boot Winbuilder Project.
I have only tested it on a Win10PE x64 build, however the script accounts for the reg entries for .net 4 on both x86 and x64
.net is not copied in this script, and I am using a script within the project for the .net 4 as required. (have included the registry entries in the event you wish to mod the script to copy the .net files yourself)
.net found in "Windows\Microsoft.net" however only a portion of the folder is required
save the code below as a .script file and place in the apps folder of your winbuilder project. I am sure it can be cleaner... but it gets the job done.
created from the file list and .reg files found within the installed application.
It appears that the same files are able to be used in all x86 and x64 builds, as I did a file comparison, but again, not tested.
Of course, you can just use the already great Veeam boot.wim, I just wanted to see if it could be done. To benefit from the Veeam built wim image, just take the boot.wim and include it in a multi-boot Winbuilder Project.
Code: Select all
----------include below--------------
[Main]
Title=Veeam Endpoint
Type=script
Selected=True
Level=5
Author=WinBuilder Version 082
Credits=PEBuilder plugin - Veeam and Jamykid
[Variables]
%ProgramEXE%=Veeam.EndPoint.Recovery.exe
%ProgramFolder%=VeeamRecovery
%ProgramTitle%=Veeam
%appsource%=C:\Program Files\Veeam\Endpoint Backup\
%appdestination%=%Target_Prog%\%ProgramFolder%\
[Process]
Echo,Processing %ProgramTitle%...
//RunFromRam,%pCheckBox1%
If,not,EXISTDIR,%appdestination%Microsoft.VC80.CRT,DirMake,%appdestination%Microsoft.VC80.CRT
If,not,EXISTDIR,%appdestination%x64,DirMake,%appdestination%x64
If,not,EXISTDIR,%appdestination%x86,DirMake,%appdestination%x86
If,not,EXISTDIR,%TargetDir%\windows\Microsoft.NET,DirMake,%TargetDir%\windows\Microsoft.NET
If,not,EXISTDIR,%Target_Prog%\Common Files\Veeam\Backup And Replication,DirMake,%Target_Prog%\Common Files\Veeam\Backup And Replication
If,%pCheckBox2%,Equal,True,Add_Shortcut,StartMenu,%pTextBox1%,,%pTextBox2%
If,%pCheckBox3%,Equal,True,Add_Shortcut,Desktop,%pTextBox1%,,%pTextBox2%
If,%pCheckBox4%,Equal,True,Add_Shortcut,QuickLaunch
FileCopy,C:\Program Files\Common Files\Veeam\Backup and Replication\VeeamFlrDrvInstaller.dll,%Target_Prog%\Common Files\Veeam\Backup And Replication\
FileCopy,%WindowsDir%\system32\msi.dll,%TargetDir%\windows\system32\
FileCopy,%WindowsDir%\system32\shfolder.dll,%TargetDir%\windows\system32\
FileCopy,%appsource%vblkid,%appdestination%
FileCopy,%appsource%Veeam.Endpoint.Recovery.exe,%appdestination%
FileCopy,%appsource%Veeam.Endpoint.Recovery.exe.config,%appdestination%
FileCopy,%appsource%Interop.VeeamGuestHelperCtrl.dll,%appdestination%
FileCopy,%appsource%Interop.VeeamTransportDll.dll,%appdestination%
FileCopy,%appsource%Ionic.Zip.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.AgentProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.CatalogFsLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Configuration.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Core.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Crypto.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBAccessor.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBCreator.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBManager.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.EsxManager.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.HvSureBackup.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.CatalogClient.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.DataCollector.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.Management.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.LicenseLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Model.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.ProxyProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.PSService.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SSH.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SureBackup.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SureBackup.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.UI.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.UI.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Validator.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.VcdLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.ViSoap.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.VssProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Win32API.dll,%appdestination%
FileCopy,%appsource%Veeam.Common.Remoting.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.System.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Transport.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Database.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Interaction.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Model.dll,%appdestination%
FileCopy,%appsource%CInterop.VeeamCrypto.dll,%appdestination%
FileCopy,%appsource%VeeamDeploymentDll.dll,%appdestination%
FileCopy,%appsource%VeeamEndpointSysUtils.dll,%appdestination%
FileCopy,%appsource%CInterop.VeeamProxyClient.dll,%appdestination%
FileCopy,%appsource%boost_thread-vc80-mt-1_35.dll,%appdestination%
FileCopy,%appsource%VeeamTransportDll.dll,%appdestination%
FileCopy,%appsource%vmGuestLib.dll,%appdestination%
FileCopy,%appsource%VeeamFSR.sys,%appdestination%
DirCopy,%appsource%x86,%appdestination%
DirCopy,%appsource%x64,%appdestination%
DirCopy,%appsource%Microsoft.VC80.CRT,%appdestination%
// copy needed .net files - use .net script
// add reg entries as found in B&R
RegHiveLoad,Tmp_Software,%RegSoftware%
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\.NETFramework\Policy\v4.0,30319,30319-30319
If,%version%,Smaller,80,RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0"
Else,RegWrite,HKLM,0x0,"Tmp_Software\Microsoft\.NETFramework\v4.0.30319\SKUs\.NETFramework,Version=v4.0"
If,%version%,Smaller,80,RegWrite,HKLM,0x1,Tmp_Software\Microsoft\.NETFramework\v4.0.30319\SKUs\Default
Else,RegWrite,HKLM,0x0,Tmp_Software\Microsoft\.NETFramework\v4.0.30319\SKUs\Default
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",WMIInstalled,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",NetTcpPortSharingInstalled,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",NonHttpActivationInstalled,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",HttpNamespaceReservationInstalled,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",Version,4.0.30319
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",TargetVersion,4.0.0
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",Install,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",MSI,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",Servicing,0
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full\1033",Version,4.0.30319
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full\1033",TargetVersion,4.0.0
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full\1033",Install,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full\1033",Servicing,0
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4.0",,deprecated
If,%SourceArch%,Equal,x64,Begin
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\.NETFramework,InstallRoot,X:\Windows\Microsoft.NET\Framework64\
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\.NETFramework,Enable64Bit,1
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",SMSvcHostPath,X:\Windows\Microsoft.NET\Framework64\v4.0.30319\
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",InstallPath,X:\Windows\Microsoft.NET\Framework64\v4.0.30319\
End
If,%SourceArch%,Equal,x86,Begin
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\.NETFramework,InstallRoot,X:\Windows\Microsoft.NET\Framework\
RegWrite,HKLM,0x4,Tmp_Software\Microsoft\.NETFramework,Enable64Bit,0
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\CDF\v4.0",SMSvcHostPath,X:\Windows\Microsoft.NET\Framework\v4.0.30319\
RegWrite,HKLM,0x1,"Tmp_Software\Microsoft\NET Framework Setup\NDP\v4\Full",InstallPath,X:\Windows\Microsoft.NET\Framework\v4.0.30319\
End
RegHiveUnLoad,Tmp_Software
[Interface]
pCheckBox1="Run from ram (boot.wim)",1,3,16,50,183,18,True
pCheckBox2="Create Startmenu Shortcut",1,3,17,89,185,18,True
pTextBox1="Start menu folder (blank for none):",1,0,33,125,168,21,
pTextBox2="Name for Shortcuts:",1,0,33,168,168,21,"Veeam Recovery"
pCheckBox4="Create Quicklaunch Shortcut",1,3,18,195,200,18,True
pCheckBox3="Create Desktop Shortcut",1,3,18,213,200,18,True
pBevel2=pBevel2,1,12,-1,21,221,225
pWebLabel1="Homepage or Download",1,10,1,2,187,18,http://www.Veeam.com
pTextLabel1=Options:,1,1,10,24,105,18,8,Bold
pBevel1=pBevel1,1,12,8,43,203,31
pBevel2=pBevel2,1,12,-1,21,221,225
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: Feature Request: Built with custom WIM
I will test the proposed solution once I got time. Thanks Neil!
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Dec 09, 2015 11:16 am
- Full Name: Klaus Guth
- Contact:
Re: Feature Request: Built with custom WIM
This solution doesn't work with network shares. I built Winbuiler Images based on Win 10 RTM (64 and 32 bit). But when trying to restore from a Shared Folder I always get the message "userDomainName" and it doesn't connect. Credentials are ok and working with original Veeam created RE media without problems.
Many people use Winbuilder with a lot of own drivers etc, so it would be great to use Veeam Recovery in this environment.
Apart from the problem above I have two changes for discussion:
I think 2 FileCopy lines should be deleted otherwise a wrong version (from the installed OS instead of the PE source) od the files would be included:
FileCopy,%WindowsDir%\system32\msi.dll,%TargetDir%\windows\system32\
FileCopy,%WindowsDir%\system32\shfolder.dll,%TargetDir%\windows\system32\
And I suggest the Registry part in the script is not necessary (and may be harmful). When .Net 4.0 is included in PE (and you have to do this), then the keys were set by this.
The problem above occurs with or without these changings.
Finally some hints for building:
- include full version of .NET Framework 4.0 (in components)
- when building a 32 Bit Version use a 32 bit OS on PC (because Veeam has to be installed in 32bit version)
- when building a 64 Bit Version use a 64 bit OS on PC (because Veeam has to be installed in 64bit version)
Many people use Winbuilder with a lot of own drivers etc, so it would be great to use Veeam Recovery in this environment.
Apart from the problem above I have two changes for discussion:
I think 2 FileCopy lines should be deleted otherwise a wrong version (from the installed OS instead of the PE source) od the files would be included:
FileCopy,%WindowsDir%\system32\msi.dll,%TargetDir%\windows\system32\
FileCopy,%WindowsDir%\system32\shfolder.dll,%TargetDir%\windows\system32\
And I suggest the Registry part in the script is not necessary (and may be harmful). When .Net 4.0 is included in PE (and you have to do this), then the keys were set by this.
The problem above occurs with or without these changings.
Finally some hints for building:
- include full version of .NET Framework 4.0 (in components)
- when building a 32 Bit Version use a 32 bit OS on PC (because Veeam has to be installed in 32bit version)
- when building a 64 Bit Version use a 64 bit OS on PC (because Veeam has to be installed in 64bit version)
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Dec 09, 2015 11:16 am
- Full Name: Klaus Guth
- Contact:
Re: Feature Request: Built with custom WIM
Here is my modified version of the script (problem in connecting network shares still included):
Code: Select all
[Main]
Title=Veeam Endpoint Recovery
Type=script
Selected=True
Level=5
Author=WinBuilder Version 082
Credits=PEBuilder plugin - Veeam, guthkl and Jamykid
[Variables]
%ProgramEXE%=Veeam.EndPoint.Recovery.exe
%ProgramFolder%=VeeamRecovery
%ProgramTitle%=Veeam
%appsource%=C:\Program Files\Veeam\Endpoint Backup\
%appdestination%=%Target_Prog%\%ProgramFolder%\
[Process]
Echo,Processing %ProgramTitle%...
If,not,EXISTDIR,%appdestination%Microsoft.VC80.CRT,DirMake,%appdestination%Microsoft.VC80.CRT
If,not,EXISTDIR,%appdestination%x64,DirMake,%appdestination%x64
If,not,EXISTDIR,%appdestination%x86,DirMake,%appdestination%x86
If,not,EXISTDIR,%TargetDir%\windows\Microsoft.NET,DirMake,%TargetDir%\windows\Microsoft.NET
If,not,EXISTDIR,%Target_Prog%\Common Files\Veeam\Backup And Replication,DirMake,%Target_Prog%\Common Files\Veeam\Backup And Replication
If,%pCheckBox2%,Equal,True,Add_Shortcut,StartMenu,%pTextBox1%,,%pTextBox2%
If,%pCheckBox3%,Equal,True,Add_Shortcut,Desktop,%pTextBox1%,,%pTextBox2%
If,%pCheckBox4%,Equal,True,Add_Shortcut,QuickLaunch
FileCopy,C:\Program Files\Common Files\Veeam\Backup and Replication\VeeamFlrDrvInstaller.dll,%Target_Prog%\Common Files\Veeam\Backup And Replication\
FileCopy,%appsource%vblkid,%appdestination%
FileCopy,%appsource%Veeam.Endpoint.Recovery.exe,%appdestination%
FileCopy,%appsource%Veeam.Endpoint.Recovery.exe.config,%appdestination%
FileCopy,%appsource%Interop.VeeamGuestHelperCtrl.dll,%appdestination%
FileCopy,%appsource%Interop.VeeamTransportDll.dll,%appdestination%
FileCopy,%appsource%Ionic.Zip.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.AgentProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.CatalogFsLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Configuration.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Core.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Crypto.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBAccessor.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBCreator.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.DBManager.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.EsxManager.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.HvSureBackup.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.CatalogClient.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.DataCollector.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Interaction.Management.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.LicenseLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Model.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.ProxyProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.PSService.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SSH.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SureBackup.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.SureBackup.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.UI.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.UI.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Validator.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.VcdLib.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.ViSoap.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.VssProvider.dll,%appdestination%
FileCopy,%appsource%Veeam.Backup.Win32API.dll,%appdestination%
FileCopy,%appsource%Veeam.Common.Remoting.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.System.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Transport.dll,%appdestination%
FileCopy,%appsource%Veeam.EndPoint.Common.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Core.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Database.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Interaction.dll,%appdestination%
FileCopy,%appsource%Veeam.Tape.Model.dll,%appdestination%
FileCopy,%appsource%CInterop.VeeamCrypto.dll,%appdestination%
FileCopy,%appsource%VeeamDeploymentDll.dll,%appdestination%
FileCopy,%appsource%VeeamEndpointSysUtils.dll,%appdestination%
FileCopy,%appsource%CInterop.VeeamProxyClient.dll,%appdestination%
FileCopy,%appsource%boost_thread-vc80-mt-1_35.dll,%appdestination%
FileCopy,%appsource%VeeamTransportDll.dll,%appdestination%
FileCopy,%appsource%vmGuestLib.dll,%appdestination%
FileCopy,%appsource%VeeamFSR.sys,%appdestination%
DirCopy,%appsource%x86,%appdestination%
DirCopy,%appsource%x64,%appdestination%
DirCopy,%appsource%Microsoft.VC80.CRT,%appdestination%
[Interface]
pCheckBox2="Create Startmenu Shortcut",1,3,17,89,185,18,True
pTextBox1="Start menu folder (blank for none):",1,0,33,125,168,21,Veeam
pTextBox2="Name for Shortcuts:",1,0,33,168,168,21,"Veeam Recovery"
pCheckBox4="Create Quicklaunch Shortcut",1,3,18,195,200,18,True
pCheckBox3="Create Desktop Shortcut",1,3,18,213,200,18,True
pWebLabel1="Homepage or Download",1,10,1,2,187,18,http://www.Veeam.com
-
- Novice
- Posts: 3
- Liked: 1 time
- Joined: Dec 09, 2015 11:16 am
- Full Name: Klaus Guth
- Contact:
Re: Feature Request: Built with custom WIM
Here is the log which shows the error:
UI.VolumeRecoveryWizard.log
UI.VolumeRecoveryWizard.log
Code: Select all
===================================================================
Starting new log
Log has been started by 'MININT-PESX73\SYSTEM' user (Interactive)
Logging level: [1 (LowDetailed)]
MachineName: [MININT-PESX73], OS: [Microsoft Windows NT 10.0.10240.0]
Process: [64 bit], PID: [1232], SessionId: [1]
UTC Time: [11.12.2015 09:05:39], DaylightSavingTime: [False]
Culture: [de-DE], UI culture: [de-DE]
Module: [Y:\Programs\VeeamRecovery\Veeam.Endpoint.Recovery.exe]. File version: [1.1.2.119], Assembly version: [8.0.0.0]
CmdLineParams: []
[11.12.2015 10:05:39] <01> Info ------- Veeam Endpoint Recovery Started -------
...
[11.12.2015 10:06:11] <01> Info Remoting options: []
[11.12.2015 10:06:11] <01> Info Registering TCP client channel [bstcp]
[11.12.2015 10:06:11] <01> Error [Veeam Endpoint Backup] userDomainName
[11.12.2015 10:06:19] <01> Error [Veeam Endpoint Backup] userDomainName
[11.12.2015 10:06:23] <01> Info Disposing SVeeamBackupService...
[11.12.2015 10:06:23] <01> Info Unregistering TCP client channel [bstcp]
[11.12.2015 10:06:23] <01> Info Channel successfully unregistered
Who is online
Users browsing this forum: hoffmp and 19 guests