In our environment system and data disks are always separated such that windows is on the c:\drive, the c:\drive IIS directory is always empty and the IIS files are on the e:\ drive, the data disk.
It should be possible for the tool to connect to IIS and correctly find the installation, however at the moment the –RemotePath option available doesn’t handle this scenario.
so... ConvertTo-Dockerfile -RemotePath \\myserver\c$\ -OutputPath c:\i2d\myservertest2 -Artifact IIS -ArtifactParam Site1/RefDataService
gives error:
Copy-Item : Cannot find path '\\myserver\c$\\IISDATA\SITE1' because it does not exist.
and
ConvertTo-Dockerfile -RemotePath \\myserver\e$\ -OutputPath c:\i2d\myservertest2 -Artifact IIS -ArtifactParam Site1/RefDataService
gives error:
Get-ItemProperty : Cannot find path '\\myserver\e$\\windows\system32\hal.dll' because it does not exist.
This is similar to Issue #38 which confirms that there is also no solution to analysing by .vhd where the installation is over multiple disks. These is essentially the same, when wanting to analyse a remote server rather than a disk image.
In our environment system and data disks are always separated such that windows is on the c:\drive, the c:\drive IIS directory is always empty and the IIS files are on the e:\ drive, the data disk.
It should be possible for the tool to connect to IIS and correctly find the installation, however at the moment the –RemotePath option available doesn’t handle this scenario. so...
ConvertTo-Dockerfile -RemotePath \\myserver\c$\ -OutputPath c:\i2d\myservertest2 -Artifact IIS -ArtifactParam Site1/RefDataServicegives error:Copy-Item : Cannot find path '\\myserver\c$\\IISDATA\SITE1' because it does not exist.andConvertTo-Dockerfile -RemotePath \\myserver\e$\ -OutputPath c:\i2d\myservertest2 -Artifact IIS -ArtifactParam Site1/RefDataServicegives error:Get-ItemProperty : Cannot find path '\\myserver\e$\\windows\system32\hal.dll' because it does not exist.This is similar to Issue #38 which confirms that there is also no solution to analysing by .vhd where the installation is over multiple disks. These is essentially the same, when wanting to analyse a remote server rather than a disk image.