Sypher

Well, according to a comparison of a dutch IT company between: Local, App-V, ThinApp and XenApp: The bootup times are higher. Local apps start at least 2x faster but thats depending on the application size. For this I have the feeling that they also calculate the downloading time, but I'm not sure. Memory usage of virtualized applications are higher. The most draining one is ThinApp, Local & XenApp use the least memory Memory usage is up to 42,6% CPU usage In their comparison this is the order from Fastest to Slowest: Local, ThinApp, App-V, XenApp Memory junkies, low to high: Local, XenApp, App-V, ThinApp One of the downsides is that you don't have shell integration for applications like TortoiseSVN, 7-Zip, Winrar, Winzip etc.

Ok, I kind-of got it to work. From the WDS server you can change the boot program from pxeboot.n12 (or pxeboot.com) to abortpxe.com (or the n12 one ) However, I'm looking for a way to do let the WDS server change that specific setting after it booted the client for the first time. Any ideas on how i can archieve that?

The computers can be both new (unknown) as already existing in the the AD, but installed using a different technique. Basicly they are already "managed", but I cannot figure out how to abort the PXE boot. My Google-searches aren't producing any viable results either, but it should be possible since SCCM and possible other WDS-based installation systems are doing it. My guess is that it can be solved with BINL, but how? No clue

Hi, Since SCCM isn't really working for me I decided to create my own. After a few hours of scripting, my unattended system deployment software is finished and working perfectly. There is only one downside: if Network is the first boot device, it keeps on reinstalling. Is there a way to make WDS send an AbortPXE to the clients that do not require a reinstallation? I'd like to have an option to select the computers that have to be reinstalled. Is this possible with plain WDS?

The account that installed (and manages) everything is the Domain Admin account, which should have sufficient rights, right? That user is a member of the Local Administrators group. WAIK has been uninstalled a few times and reinstalled, I've tried various WAIK versions but all of them produce the same results.

I've already done that multiple times, both with and without RUN AS. There is no difference, both times the image creation fails.

This only happens when the ConfigMgr MMC is not being "Run As" Administrator.. Apart from the crash, there is no real difference. Either way, it still won't create a MDT-Bootimage..

The screenshots posted before are with run as Administrator

Win2k8 Enterprise x64.. But the integration is working, since I have the options available.. It fails when I try to generate a boot image for MDT2010. And after pressing OK:

Thanks for your reply anyweb Indeed, its the SP2 RC from MS Connect.. They have been integrated using the startmenu item. Run as Administrator isn't really necessary since I'm logged in as Domain Administrator, right?

Hi, I've been evaluating the use of SCCM - err ConfigMgr like Microsoft would like you to call it - and I've came across MDT 2010. This seemed interesting so I've installed it. I was running R2 but since I've read it requires SP2 I've upgraded my installation. This however did not change the situation. I am trying to generate a MDT Boot image from the SCCM mmc. This process is working hard and then suddenly complains that "The ConfigMgr reported an error". Geeh sparky, seriously? Really informative smsprov.log states the following: Google nor this site's search is giving me any useful hits. I was wondering, does anyone know how to fix this? I tried downgrading WAIK but this didn't seem to work either. Looking forward to your replies! Thanks in advance. Sypher