right now im testing too on a clean VM (im posting my findings in a different thread)…
i noticed there is a progress indicator.
I also noticed that in: C:\PROGRAMDATA\AVAST…\ there is a log file even if the installer fails prematurely… that path is for a win7/vista/2008 machine tho, dont know for sure where it will be put on an XP machine.
Post that log if your installation fails again (or if you can find the logfile from the current one)
Mirror should be running without any need for you to interact. The initial download of the mirror is carried out during the install phase, so once set up, you should be fine.
The service itself runs as a .NET process, capable of running both as 64bit and 32bit application. For this reason we have two copies (two versions) of some binaries. You need not worry, the correct one will be called by the SBC service.
you cant push a deployment if you have not installed the mirror. The mirror contains all the client installation files (jx correct me if im wrong). You cant push something that is not there yet…
I done with installation on XP SP3 memory 1024MB, harddrive C: 10GB and D: 4GB, Netframe 3.5 sp1, Netframework 2 | 3.5sp1 | 4, MSSQL2008 express on VM
installation take time if you not use genuine windows license.
MSSQL2008 express requiered windows power shell and if you doing installation from microsoft website it will check your windows genuine.
and I also have the problem with installation fails prematurely… but it solve after install the power shell and reinstall MSSQL2008 express.
i have finish the mirror, now i do the push install the report said 'succes" but there is no any installation on the PC target.
i can’t found any log file for push installation logs
installation takes time, no mather what kind of WIndows license… i assure you, my licenses (Volume License and Technet licenses) are all valid
The problems you ran into with that, are specific for installations on an XP machine (hence my request to drop support for installing SBC server on an XP machine in the other threads)
edit:
like i said… i dont know where the logs are placed on an XP machine with SBC…
did you configure the target machine with:
FIREWALL OFF (to test)
FILE SHARING turned on?
can you access the targeted machine from the SBC machine with: \targetmachinename\c$ and \targetmachinename\admin$
ps: right now im running into deployment problems myself too, still figuring out to work this out
let you know in another thread that i am posting later