• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About FastRedPonyCar

  • Rank
    Fixing Airforce IT problems one patch at a time...
  • Birthday 05/15/1981

Contact Methods

  • Website URL
  1. thanks I'll give it a shot
  2. I've been trying to wrap my head around imagex and it seems so simple in concept but for some reason, I'm having the hardest time understanding how to capture an image with it. there's some concept it seems with the capturing process that the windows AIK help file documenting how to use imagex and all of the online how to's I've read seem like they're almost assuming that I know how to do something important that I'm not. I'm missing out on some concept that I feel is just absent from these tutorials. Here's where I'm at. I've got a laptop I've installed and customized vista on and sysprepped. I've used AIK to build a winPE disk with imagex and a generic config file for file exclusions and I can boot that disk into winpe, browse the disk and see image x. I'm trying to run the command they give to capture the image but it doesn't seem to be working. Now... here's where I'm confused. They say to run the command prompt for imagex on the technician computer (which is my main computer with windows AIK installed on it) but how am I supposed to capture an image of the laptop sitting next to me on the desk if I'm opening up imagex on my main "technician" computer??? also worth mentioning is that I've got the laptop hooked into a switch that an image server is attached to. I've tried running Net use m: \\servername\images$ (where the images are stored on C:\images$ on the server's hdd) and I get the error "the network name cannot be found" It's part of a workgroup called "pcconfig" so I tried Net use m: \\pcconfig\servername\images$ and it says "the network path cannot be found" Is there some big picture concept that I'm missing here?? Please help! Oh, Also worth nothing is that I can boot up norton ghost and capture or load images from that same images$ share so I know there's nothing wrong with the hardware.
  3. I hear it's not when you're a MSDN member/tester... which I am.
  4. I'm rocking 6895 here also. I've tested a few various Vlite builds of it on 3 different systems. My main one is my HP 8510p notebook, another is a Dell D630 notebook and the 3rd one is an ancient Gateway E series that has 1 gig of ram and a 2.4 ghz PIII cpu. I'm shocked at how fast this OS runs. I thought folks were just blowing smoke when they claimed it was as fast, if not faster than XP. Man they were right. On that Gateway, straight out of a fresh install, it's a hair quicker than a fresh XP install with all patches and SP3. A few drivers that aren't supported (intel video drivers) but it does a nice job of stopping the loading process and asking you to go to last known good config. The interface runs smoothly on all systems as wel. Much quicker using Aero than with Vista and system resources are more or less almost all there. I'm also getting that error with the unattended setup though. It's not a huge deal though. I'm going to try to run a sysprep proceedure like with vista that has all of the info filled out to see if it works or not.
  5. I'm not sure about the registry stuff but KB838804 is supposed to be one patch for this.
  6. yeah that would be it. Apparently my name and phone number made it's way up into the upper eschelons of Mcafee's support team and they're going to be calling me sometime soon. One tidbit I was able to gather though was that there's something to do with the kernel running out of space and increasing the kernel size or adding a kernel size key to the registry MAY fix the issue.
  7. We've recently deployed HBSS and our Server 2K boxes are bluescreening. I got an email saying that there are issues between win2K servers and HBSS when using remote desktop and HIPS (Host Intrusion Prevention System), There was mention of a hotfix released that addresses this problem but I'm having trouble finding out which hotfix it is. any of you guys know which one we need?
  8. Let me bump this old topic up as it's something I'm trying to figure out here at work. Windows updates is disabled via registry/group policy settings. Our lab managers can't change them and are required to update machines with microsoft MBSA 2.1. The scan runs fine and returns the results saying what patches you need. Rather than downloading exe updates, it only will download cab files for the MS08-XX update. Is there any way to get MBSA to download the actual EXE file rather than a cab file or is there something I'm supposed to do in vista to install these updates using the cab files it gets? I swear 2.1 is the dumbest thing ever. 2.0 worked great, grabbed EXE files and just did what it needed to but it's incompatibility with Vista sucks.
  9. Sorry I forgot to mention that! The images we get have the group policy and registry locked down so that the windows updates are disabled (as we use SMS to keep the machines up to date) The problem is that we USED to be able to use our own images that were kept up to date and now we can't so we're trying to find a faster way to get a machine up to date before putting them on the network. Anyways, I found this. Works BRILLIANTLY (and faster than windows update)
  10. Ok I've got builds of both 32 an 64 bit vista and I'm looking for something that can be run after an install (which includes SP1) that can automatically go and grab any updates and install them without countless pesky UAC prompts. Does such a tool exist? I've installed MBSA 2.1 on one of each and it shows what the machine needs patched but the download link goes and grabs a cab file that I have no idea what do to with. I've gone out and manually downloaded the actual MS08 exe files but with around 25 of them needed after a clean install, it's tedious and time consuming and I need something that can do all of this automatically. Any ideas or programs that can help speed this up?
  11. OK some guy brought a dell precision 360 desktop into our shop and it has a SCSI hdd adaptor and 2 western digital IDE drives, each in an SCSI cradle that plugs into the SCSI to IDE adaptor. I was fairly sure I'd need to do the whole F6 to load SCSI drivers before XP install begins but before the machine even POSTS, it comes up saying no primary HDD found. Bios says "unknown device" as primary IDE drive. The actual harddrive is perfectly fine as I took the drive out of it's little SCSI adaptor module and just plugged it straight up to the mobo with an IDE cable. It's loading XP right now. The problem is, there's a 2nd hdd in it's scsi tray that he wants XP on as well so that he can do the whole hot swap thing with the drives. I don't have another SCSI to IDE adaptor around to try and see if the actual adaptor that these hdd modules are sliding into is bad or if there's just something I'm not doing to allow the PC to SEE that adaptor. Can anyone shed some light on what could be wrong here? BTW, I hit up dell's site and downloaded the scsi drivers, put them on a floppy , loaded them with F6 before the xp install but it comes back saying no hdd found to install the OS to.
  12. FIXED!! I deleted C:\WINDOWS\system32\drivers\WimFltr.sys Then re-started Vlite and told it to install, then I selected ultimate again and now it's good (hopefully to stay)
  13. I've got the X86 wim filter in the X86 program files Vlite folder, I've right clicked on the X86 file to install the driver. Vlite fires up fine, sees my files on the desktop that I copied from the dvd and then when I click ultimate, I get the mounting image error -code: -2147024894 It asks to restart which I've done twice. What am I doing wrong? search function yielded nothing Edit: I'm running vista 64 to do all this.
  14. because if you do SP1 then hotfixes, you'll get the ntoskrnl.exe corrupted error message when it loads the setup files. for some reason, it works when you integrate the post sp1 hotfixes first. I slipstream SP1 and then integrate the hotfixes and I have never received any error when installing. have you removed any components and still had it install without errors?
  15. because if you do SP1 then hotfixes, you'll get the ntoskrnl.exe corrupted error message when it loads the setup files. for some reason, it works when you integrate the post sp1 hotfixes first.