• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About jfield

  1. Fixed. So happy. It looks like what happened was that because this was an image of a machine built on SP2 and then upgraded to SP3, RIS was pulling files from the SP2 flatfile and not the SP3 one. Uninstalled SP3, riprep'd and everything is fine now. I'll just built an SP3 image later, for now WSUS will have to handle it. Thanks!
  2. I just redid the image with no drivers other than what was in the image when I created it, and it is doing the exact same thing. It is like the act of imaging it somehow corrupts the install. Something changes between what the system looks like when I use riprep and what it does when being imaged. I don't understand. I've imaged hundreds of systems, probably 10 different models of machine, and never had problems like this. I'm at a total loss. Also, it won't even boot into safe mode (without networking). Doesn't that pretty much eliminate the possibility of it being a driver issue?
  3. Nothing other than the text mode drivers and whatever is in the image itself, but all of it worked on the machine I did the initial riprep from. Something happened between riprep and the image being brought back down. I just can't figure out what.
  4. Hello everyone, I have spent the last ~2 days trying to get brand new out of the box Dell Optiplex 755s working with RIS. I don't understand how I'm having more problems with this one system than I have with all others Dells I've used with RIS combined. The problem, as it stands, is this. I have the Optiplex 755 SATA set to "ATA" or "AHCI", neither matters. I download the image (A fresh one or an existing one with the appropriate drivers in the TEXTMODE folder) by PXE booting to RIS (WDS Legacy mode, its a W2k3 SP2 server). The image downloads perfectly, and then when the system reboots, it goes to the Windows logo and reboots after a few seconds. This happens both with a preexisting image I've updated and with a brand new image I just built on one of these machines. It reboots over and over. If I attempt safemode on the new image, the lockup will reliably occur on either cdrom.sys. I tried disabling the cdrom and it did nothing, I imagine its not cdrom.sys causing this but I suppose it could be. I'm losing my mind here, and I'm facing Monday with a lab that was supposed to be up this week still down. Any help would be greatly and truely appreciated. If I get any suggestions I will go in Saturday afternoon and try them out. Thanks, -Jeff
  5. This is what I get for deploying an update after a short testing period... Anyone have a solution to this or do I need to roll back SP3 on all of my machines? Kicking myself at the moment.
  6. What error are you getting? Check http://www.msfn.org/board/index.php?showtopic=84496 you might be seeing the same issue I am? -Jeff
  7. Since this previous Patch Tuesday, we are having intermittent problems with Word not opening and throwing the error "there is not enough memory or disk space to run word". Now, first thing, there is enough memory - nothing is taking up a lot of GDI object or Virtual Memory, and there is 100mb+ of physical memory free. There is 27GB or hard drive space. The page file is only 20-25% utilized. I've tried deleting Normal.dot, doesn't seem to have an affect. It also seems to affect other office applications in different ways - I get nothing from Excel for instance when this is occuring, not even an error, it just doesn't open. After some additional diagnosing, it appears rebooting fixes the issue, but only for the first user that logs in after the reboot. I've advised my users to reboot when they log off, but that isn't a very elegant solution. All signs point to it being one of the critical patches WSUS pulled down this week - but has anyone else run into this, and if so have they found out which update it is or found some other solution? I've checked experts-exchange and the MS newsgroups, as well as several forums and haven't found a solution yet that has worked. Platform is XP SP2 with Office 2003 and all current updates. The machines are members of an active directory domain. Let me know if there is any additional information I could provide that would be helpful. Thanks, -Jeff
  8. Ok, that volume is excluded entirely. I will update this thread after I test out the changes this afternoon. Thanks!
  9. A little more information and a couple more questions.. I'm certain its a memory leak as I'm getting Event 2019 repeatedly from the Srv process. My problem is I don't see any huge increases in my pages/nonpaged pool, my thread count or my file handles. handle count 20892 pool nonpaged 884792 pool paged 3227756 thread count 916 pf usage .97gb Top Process: lsass 255mb System hanbdles 2207 threads 66 Lsass seems a bit big to me, but 256 mb isn't all that big. When this problem happens, I can't even run ping because its out of memory. Interestingly, the system still shows a gigabyte of memory "available", and only shows the page file have 970mb or so used. The event: Event Type: Error Event Source: Srv Event Category: None Event ID: 2019 Date: 9/11/2006 Time: 7:54:28 AM User: N/A Computer: xxxx Description: The server was unable to allocate from the system nonpaged pool because the pool was empty. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 00 00 04 00 01 00 54 00 ......T. 0008: 00 00 00 00 e3 07 00 c0 ....ã..À 0010: 00 00 00 00 9a 00 00 c0 ....š..À 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 18 00 00 00 .... I've got that repeated since we imaged about 25 systems on Saturday until this morning when I came in and rebooted. I've downgraded the antivirus to the version we used last year, but I've always excluded the "RemoteInstall" folder - do I need to exclude the entire RIS volume? I wish I had the money to seperate out our services, this box handles a lot for us, but its never been a problem in the past, last year I could images 50-100 machines a day and the server would never flinch, so it has to be a change I made or an update made. I'm still leaning towards the AV software, we'll see how the downgrade goes. It is also running a fully updated backup exec 10d, thats my next likely suspect I think. Any other thoughts? Should I disable AV scanning on the entire volume the RIS images are stored on, or is excluding RemoteInstall enough? Thanks, -Jeff
  10. Symantec Antivirus Corporate Edition Server 10.1 was recently put on there in place of 9, I'm leaning towards that. The Machine also has Backup Exec 10d on it and I'm making sure the latest updates are installed for that. The machine receives critical updates through WSUS automatically. Leaning towards Norton at this point. On the last crash, it indicated there was a memory leak somewhere (Event 2019) so I'm going to try to replicate the problem yet again and track the memory usage. -Jeff
  11. I am having a new problem with my Windows 2003 SP1 RIS server, a Dell Poweredge 2650 with a 2.8GHz CPU and 2 gigs of RAM on 100/1000 megabit switched network. I used to be able to RIS as many systems as I wanted, but now at about 15 systems my server will slow to a crawl, and then eventually drop network connections entirely. Sometimes, the "System" process will be using 100% of the CPU. I haven't made any changes other than Windows updates. Has anyone had anything similar to this? Thanks, -Jeff
  12. Hello, I have a Software Restriction policy going for my OUs and it is working great except for one problem - though I have removed LNK/URL files from the list of restricted extensions, it has had no effect. I've tried adding them back in and removing them again. I know I am in the correct area of the GPO (User\Windows\Security\Software Restriction Policies) but changing it has no effect, and I don't have any other Software Restriction Policies, they only exist within this OU. Is there something I am missing that I need to do to exempt LNK/URL files other than remove them from the list? If I specifically exempt these files using a path entry, it works, but only for whatever directory I specifically state in the policy, and I would rather not do that as I would like the users to be able to organize their shortcuts in folders and such. Does anyone have any experience with this sort of problem? Thanks, -Jeff