fizban2

i'll add a third... and thats about it cause all the good point has already been covered

another link with some really excellant info Windows Server System Reference Architecture (WSSRA)

sence indeed, also remeber alot of things were rewritten TCP/IP comes to mind and the way that hooks are placed, not so much an issue with AV as it is with firewall software but for scanning mapped drives and across computers it makes for a problem. now why do you consider that it is a critical flaw that no currently running AV will run on vista? i would think this means the MS is trying to revamp things and make them better (hopefully) which means that AV groups will have to rewrite their code to work with vista in the process making it better, anywho just for kicks Symantec AV Vista Client Mcafee AV Vista Client

defiantly agree with you here, it would be better to wait for beta 2 to deal with a more reliable and less bug ridden code, but i know alot of early adopters and such will be testing it as soon they can to get the most jump on implementation. I know we have a test domain for vista/longhorn and test the mcafee vista AV agent there, because eventually when we ahve to migrate 4000+ pcs to vista, we want to have as much advanced time working with it to knock as many bugs/problems that we can out of it, not to mention just to have the face time with the programs to see how they act/react. but i will agree, for most people an AV makes little sense, it is a beta anyway blow it away and reinstall if it gets mucked up B)

you are right there, many things are still changing but on the same note 5308 is now feature complete so we should just be seeing bug fixes and the like, on the same note with all these changes AV companies have alot to change with too, they have to build an new AV agent for based on a beta product, so there programs may or maynot work but by testing them you can get feedbacl to those companies to help them get them working on vista. not that nessicarly that you need AV to prevent against virii and such but more to get it working/runnning smoothly with vista itself. Providing different environment and the like for AV companies to get experience and input from will help them plan and avoid headaches in future builds, again GSM you are right, installing a AV just to deal with viruses doesn't serve much purpose but to help the development of those AV products is another case

could you explain the question better? i am not sure what you are going for.

since 5308 is feature complete new version will probably be able to be installed ontop of it, but as GSM says, it is buggy, you are better of formatting and starting fresh, being a beta it will have its own issues now matter what, better to only have the issues of the current build and not the ones of the previous one also

not so nessecarily a waster, for corperate is is nice to see how beta versions of AV that they use now will work in there current environment and what changes they have made, allows them to see bugs coming and such, also allows for input to the AV companies on things that they would like to see in the next version, just like with MS betas. @xgman sadly i do not have one yet got the program from my manager, i can check with him to see what kind of deal we have going on with mcafee on it though

thanks for explaining better yesterday was insane and i did have a lot of time to post anything longer..... crazy end users.....

the client software is actually built into the setup.exe for vista, which is why you need to use a vista PE boot.wim, the files are also created for you in your WDS installation look in the REMINST\boot\<osversion>\ there will be the pxe files that are created there, those will need to be copied to your own custom PE if you wanted to use another other then a vista boot PE, the files would go in the Windows\boot\pxe folder on the PE, here are the files that are needed, abortpxe.com bootmgr.exe hdscom1.com hdscom1.n12 hdscom2.com hdscom2.n12 pxeboot.com pxeboot.n12 wdsnbp.com those should be found on the WDS\REMINST\boot\<osversion>\should be in there

it being a beta means that isn't possible once it is out of the beta stages it will be available for everybody, plus that is against the rules of the forums

agreed albuquerque, if you install ximage on vista 5308 it will mount images fine. still can't figure out why it won't on XP though..

if this is happening for several programs i would check to see if the ram is also faulty, or going bad, bad sectors or ram would cause this if the program was suppose to be written there and that space is no longer available because it damaged or bad

mcafee has a beta that you can get from them, runs soso, kinda slows down the machine though....

followed the same instructions that you did, from teh help file, i copied the boot.wim to my working folder and tehn applied to to the build folder, added the files that i needed and installed the packages witht peimg, the /prepped the folder, at that point i compressed it back to a wim and it worked fine, i got the error that you were speaking of the first time, recopied my files from the windows AIK folder to the directory i was working with, reran through the steps and it worked the second time, i will try it again and see if i can recreate the error

it would think that once you sysprepped the machine that those changes would have dissappeared, i don't remeber all that sysprep removes though... anyone else?

problem fixed, virtual pc required about 300 mb to runn correctly, wonder if it just cause i have 3 machines running at once... anyway working swettly now

by the by, has anyone had any luck moutning a wim image and viewing it correctly? ximage 5308 doesn't seem to let me so easily... getting errors about the location no longer exists

ok, got wds client running in the PE now, but getting errors with the setup.exe. this is all running on a virtual server (3 actaully) but i think it is just a memory issue, any thoughts? Error ----------- the expection unknown software exception (0xe0000100) occured in the application at location (0x77e4028b) -----------

running from XP should be no problem, i built me 2 pe's from my XP machine, actually ximage doesn't run so well on vista, the filter does work right on it.... anyway it runs fine on XP, no which WIM are you using for the base? or you using the boot.wim or the winpe.wim to start with?

ahh but i didn't say which icon had been changed now did i ;P

the peimg with the /prep switch should not have failed this probably where you are getting hte error, try running through it again from the start, fresh files, (wim etc) see if that takes care of it

try using ximage to verify the PE, i had this same issue and i recreate my PE from the winpe the comes with the WAIK and it worked fine then

OK, figured out the PXE boot, if you apply the vista 5308 boot wim to a folder, you can see the structure needed to make a bart PE pxe bootable windows\boot\pxe\*.* in the folder that you created you will see 5 folders programfiles program data sources Users Windows copying the contents of the pxe boot folder you can use this to boot you win pe's to the WDS server got an error trying to run my install image though, will be working on it to see what happend also side note, those files in the PXE boot foler on the vista boot wim are located on the reminst directory that you created for the WDS under \reminst\boot\x86\ all the files you need are there. as for the XP image, is just a XP sp2 image that had been syspreped, that is all, i think i need to look more in RIS to get this working right,

Question, Is bits (background intellegent transfer service) installed by default with XP? or does it have to be installed manually? i have found a patch to go to bits 2.0 but not sure it the intial version is installed Thanks in advance