Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

aschwartz

Member
  • Content Count

    13
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About aschwartz

  1. I figured it out, instead of using the cmdlines.txt file, I added a new line in the guirunonce that does the same, populate the runonce upon first boot. I just had to add a shutdown -r command in to make sure they take affect. I then created multiple sif files, one for each image I wanted. I didnt need a copy of the directory again.
  2. I think I have a better idea of what I need now. I think that I need to know if there is a way to set it so that I can run a different cmdlines.txt file with a different image. Meaning that - my directory structure looks like this: \RemoteInstall\Setup\English\Images\ Under here I have 1 folder called winxpsp3_1, which houses 2 folders i386 and $oem$ In the i386 folder there is a templates folder which has the ristndrd.sif file(there is also one in the i386 folder) The $oem$ folder has the cmdlines.txt file as well as the runonce.cmd file that the cmdlines.txt file calls. What I am looking to
  3. Is there an easier way to create a 2nd image, with just a different runonce (or cmdlines file I should saay, which calls the runonce? Am I doing it incorrectly.?
  4. I have a working RIS server, with one image that works perfectly. network boot to fully installed and patched with no user intervention. Its a beautiful thing, and I couldnt have done it without help from this site thats for sure. But now I have an issue. I want to create a few new "images" for install and that are listed on the boot menu. here is what I did. Under remoteinstall\setup\english\images, I took the folder of my image (called WinXPSp3_1) and copied the folder. renamed the copy to Vanilla XPSP3_1, and then went in and modified the \i386\ristndrd.sif and i386\templates\ristndr
  5. I had tried the newest LSI drivers from their site http://www.lsi.com/obsolete/lsi20320_3157.html and they still were not recognized. I did more research and it seems that some people are having problems with getting the LSI driver to work. I tried to create a new VM using the buslogic driver instead of the LSI, and the same thing happened.
  6. I have my RIS install (Legacy mode) for xp sp3 running very smoothly. I can get it to pxe boot, then install xp, then install about 6 apps that i have and everything works correctly. My problem is that this works for physical machines, but I want to test with deploying xp to a VM on an esx host. I perform the pxe boot and it connects, but I get the dreaded message regarding the hdd not being found. SO apparently i need drivers. I found a site that had a flp image for the LSI and for the buslogic drivers, but when I dropped the cat and sys files into the i386 directory and then restarted t
  7. I was actually thinking of using regmon and seeing which registry entry it modifies, and then modifying that for all users so it starts disabled, that might do it. Thanks for the help.
  8. This site has been great for me and my RIS server, I have my build almost complete, and this is the last app I need to integrate. I was told I need to add the salesforce plugin for outlook into the build, but it needs to be disabled upon install, so that it can only be activated if needed. So I have an msi and an exe, and I can install them both silently, but when I open outlook, it starts the salesforce plugin wizard thing, and I dont want that. Is there a way to install a addin for outlook, and have it be disabled? I guess there might be a registry key for them, but I am unsure of where or
  9. I used Cluberti's version, and it worked perfectly.
  10. Apparently the code that I was using was valid, but not working in the setup process. I tried another that I had, and it went thru, so I got it to deploy from barebones to the desktop with no intervention, which is a great step. Now I have to do apps, which should be interesting. Apparently I can reply to my own posts quite nicely. lol.
  11. I think it was that the network driver wasnt loading, that it went into that setup, because I redid the image creation, and it recopied the i386 directory, and I recreated the $oem$ and below structure, and redid the drivers, and it didnt prompt me anymore for the display settings nor did it require me to go thru the mini setup. It didnt take the product key though, so I am not sure why, because it takes it if I put it in manually, just not thru setup.
  12. Also, I noticed that in the server properties under the WDS in admin tools, on the tab labeled Client, the enable unattended installation is checked, but there is nothing in the boxes, and I couldnt find any xml files to put there. I assume that this is for vista only, so its not a big deal, but I figured I would mention it. Also, since I didnt mention it before, I am using legacy mode (or mixed I guess) I am going to just use this for xp deployment, and the apps will be installed after via GP.
  13. Hi all. This site is great, and I am new to using RIS. I had used LANDesk to deploy images before, so sysprep and what not are nor foreign to me. Here is my situation. I just installed a RIS server on a 2k3 box, and am able to install xp on a pxe booting machine. My first issue is that it prompts me for a username, the org shows up correctly, but the name field is blank. In the .sif file, I have that entered, so I am unsure of why it doesnt work. My next problem is that the install goes thru, but it prompts me for the display settings (Windows will now change your display settings) and t
×
×
  • Create New...