M0NKEYPWNAGE

In Netherland they got a term/treatment for special people like that called postabortion and preventive dispossal/cleanup. Oh, btw with special I mean dramatic and attentionwh0re like, not gay.

Hi, I'm Dutch, from a town called Deventer, you?

You should look for Windows Registry entries, parameters and values for taskbar positioning are all saved in the register, I'm searching for solutions for Windows tweaking too, haven't found any though.

I didn't get so far as getting it booting with F12, did you do anything to get that or is it just the PXE-NIC-thingy? Anyhow, to answer your question: WDS has several modes, mixed, native and legacy, I think you need the last one.

Well I wouldn't follow Microsoft's Guide, haven't gotten any usefull information from 'em now that I think of it.. Well the Quick Guide was okay but I really can't think of anymore. To put it simple, first download all the stuff, way handier, saves a lot of time and frustrations: Install Windows Server 2003 Install SP2 Install AD, DNS and DHCP (configure too) Install some other apps, come with SP2 most of the time. Install WDS which came with SP2 (Windows components) Install BDD2007 Install WAIK (Don't nail me onto it if I've forgotten something, I haven't had my coffee yet. ) Start fiddling around. In the Quick Guide is explained how to do your first installation with an CD etc. Other documentation is in above posts too: lazyadmin & deployvista.com (is secretly also deployxp.com ) Oh, in my other topic I also placed that I added my first app: Adobe, how I managed to do that you can read at lazyadmin too. It's quite simple, the installation 'script' from the unattended guide won't work for WDS, so I really hope that there will soon be an guide for that here too.

Sure, but here's two links: Google for lazyadmin(.com probably) and deployvista.com, the second sites has 4 tuts. There's also something from Iowa or something but there's just too many things done in it without explaining any of 'em so I don't recommend that one. I'll see what I can do before and during this weekend.

Got drivers working, got my first app working. Now finding a solution for Office 2003, Microsoft doesn't support deploying Office 2003 because BDD and Windows are targeting their latest product: Vista and Office 2007, rather frustrating. BDD SE (standars edition) doesn't even have the deployment bench so I'm stuck with BDD2007. Anyhow, I'm still very glad that I managed to add Adobe Reader 8, a big step into the right direction.

The same in a few ways, instead of using an CD a Windows 2003 Server, WDS stands for Windows Deployment Services, RIS: Remote Installation Services. It's used by OEM's and companies. Here a big tip: don't even try it. I can't place the apps in BDD2007, very frustrating. I do know there are several updatepacks, dutch too if not mistaken. Anyhow, thanks for welcoming me. Maybe I'll be able to find the pack again, when that happens I'll let you know.

If there is one IT site on the world with relative much Dutch members is it MSFN You're a young Dutch but not the youngest, I'm 16 Welcome Oh neat, so what are you doing here, also gaining information about unattended installations or is your field of interest more ...extensive than that? Dunno what this forum is all about, have been busy with WDS (new version of RIS).

What Henkes said is pretty much correct, but it's recommendable to start of with something basic: an bare Windows-deployment. Later on you could experiment with extras.

Probably has something to do with the Active Directory, I think you should make users which have enough permissions and rights to enter the maps necessary for deployment.

He doesn't use RIS but WDS. Are you using BDD2007 of Standard Edition? -2007 has an neat builder which is pretty handy, you can add drivers to it too, Bâshrat the Sneaky's DriverPacks are something you should take a look at. You can simply add them to BDD2007 with Out of the Box Drivers, makes an big list which is rather unorganized (atleast mine is) but it works.

Loving the dud. B)

w00t, first reply, already worried about living in the wrong time zone.

Finally I can respond, IE7 is giving some troubles with the lay-out, anyhow, here's what I wanted to say: I guess I try more when at home again, tried different things with the AIO, but I think making different 'programs' is better, I'll give you more info later on that. The problem I had at work was adding drivers, I try stuff at a small IBM-PC, now after adding Office the connection couldn't be made because of the missing LAN-driver. Added a bilion drivers which happen to give an error during the deployments I currently am trying. Do I need to rewrap the build or what? In the mean while I'm gonna try some stuff, here's the error: ZTI-Error Undhandled error returned by Z:\Drivers: Object required (424) ZTI-Error Undhandled error returned by Z:\Drivers: Object required (424) Non-zero return code executing command "X:\Deploy\Tools\X86 \TsmBootstrap.exe" /env:SaStart, rc=-2147467259 No more Error.

Hi Henk, it's me, kid Trouble again. Next obstacle I ran across is about the quietinstall line from beheerportal.nl, I've got an Office 2003 AIO VLK CD, with 2 serials, one for the regular office apps, and another one for Frontpage, Visio, Project and OneNote. I found this on Google http://www.msfn.org/board/index.php?showtopic=20970: Note space before "The option.." that shouldn't be there, right? Anyhow, I thought doing the following per application edit the SETUP.INI: So I'm having the following in my CD: K:\FRONTPAGE\FILES\SETUP\SETUP.INI K:\ONENOTE\FILES\SETUP\SETUP.INI K:\PROJECT\SETUP\SETUP.INI K:\VISIO\SETUP\SETUP.INI Should these all be edited? [Options] PIDKEY=SERIAL Maybe even the general package itself: K:\OFFICE\FILES\SETUPSETUP.INI. Edit: Took al look the files: [Options] ; The option section is used for specifying individual Installer Properties. ;USERNAME=Customer ;COMPANYNAME=my company ;INSTALLLOCATION=C:\Program Files\MyApp Seems that the extra space ain't an typo after all and I just have to place the PIDKEY. Edit 2: Alle bestanden van de ISO naar een mapje gekopieerd, daar die zinnen er in gezet. Nu een ISO maken vinden. Forgot it was an English forum, sigh.. The above means: Copied all files from the ISO to an map, inserted all lines. Just have to find an ISO-maker now. Edit 3: No need for an ISO, just copied the files to the server and had BDD 2007 pick them out, just having the setup.exe /i Pro11.msi line now, I hope it's enough, I doubt it tho, because the Setup.exe is rather abstract.

No problem so far, just an update. Managed to add Microsoft Office to BDD, the deployment point is updating at the moment, I'm about to go home in a few minutes , then I'll read further, I think I should now make WinPE2.0 boot from the network instead of the CD, because I don't have any CD-R's left at work, lmao.

Thanks Henk, I'll run it through, not experienced at making .bat's etc. but I'll give it a try, if I get stuck somewhere you'll be the first one I'll bother, ke? Omfg (is that allowed here?), I've had that site bookmarked, never found that particular page though.. D'OH! Helped me out alot, looked at the wrong places again.

First of all.. I've thought a while about posting this, made the text under thise alinea in an random document constantly editing and added extra information making it as clear as possible. If anymore information is needed I'll add it to the OP. Hopefully you guys can help me out. Personal background Hi, I’m a student running internship and the job they gave me is build an server which deploys Windows XP (SP2) installations including software like updates, drivers and applications. Current situation This is what I’ve done so far: Made an LTI-setup, WDS, BDD 2007, WAIK, AD, DNS, DHCP installed, configured and running on Windows Server 2003 SBS with SP2, the thing finally works now, didn’t realise for a long time that the annoying Windows Firewall wasn’t shutdown. The whole thing is set up BDD 2007 Quick Guide, so far it's pretty basic, it just installs Windows XP and Service Pack 2. If it’s any use mentioning: SP2 was included in the files on the Windows XP-disc. Ran deployment a few times using Windows PE 2.0 on one or two clients, all of those deployments where successful. Maybe it’s wise to try to deploy XP to other clients with different hardware too before trying anything else? At the moment I just want to make Office 2003 be installed during the XP deployment. Final Goal An server that can deploy Windows XP as unattended as possible on a wide variety of client containing different hardware. Software like Office 2003, updates and drivers also have to be deployed with the XP-deployment. Saving images of each workstation is not an option since too much different computers come by. Also using F12 instead of the WinPE 2.0 CD is something I’d like to do. ZTI seems not to be an option because SMS 2003 is too expensive for a student and without it, Office and other applications should be deployable too, right? Another reason not to use SMS is because it’s too big, not in disc space but in options, I’d probably lose any sight of the right direction I’m currently following. Later on being able to do the same with Windows Vista and Office 2007 would be a nice extra. Other things On deployvista.com I’ve read something about the XP-uberbug, what’s up with that, should I actually take notice of it or just treat it like another hoax and ignore the thing? I haven’t tried unattend-files and stuff yet, because I don’t know in what situation I should use them and I’ve no experience coding, did little stuff with html but that’s it. Late notes/final question/summary Where the hell should I begin, running through the documentation of BDD 2007 (over a thousand pages) and installing even more services and applications don’t seem to be the solution.

Hi all, Just registered today because I think that this forum will provide better support than MSDN. I'm 19, running internship as an administrator at a small networkcompany which places and takes care of network infrastructures. Explanation for properly pronouncing my nickname: M0NKEY.. Makes sense so far right? Pwnage is Ownage with as you see an P instead of an O. An typo commonly made, mostly on purpose by gamers and such. Most unlikely that I'm the only Dutch one here, so I hope to meet other regulars from the red light disctrict soon because English ain't my strongest point.