cluberti

If you're using RIS, the installation screens can be customized (they're text files, basically) and bringing vars from RIS setup through to the finished image was fairly easy to do. However, WDS is NOT a full setup engine like RIS was, but runs WinPE images which do the heavy lifting - so unless you're launching your own WinPE that has it's own customizations (or use one created from another source that does this already (like an MDT or SCCM boot image), a boot image imported directly from installation media isn't going to prompt you for much other than user/pass, images, and drive to install to.

PM sent.

Happy B-Day my friend. Hope the hangover is nonexistent.

Well, this one looks like it might be the file itself as even the .dmp you uploaded is corrupt. For what it's worth, the smallest minidump I've ever seen before was ~278K - I've never personally seen a 64K minidump before . Do you have a paging file configured on the \Windows volume?

Without being in a domain environment, you aren't going to be able to lock this down to one PC at the share level, only users.

I'm not sure, but I think that is probably OK under the licensing terms as long as the user getting the machine is given a copy of the CD you used in case they needed to use it again. I personally would not be doing it (because you're already voiding the EULA) and would be using MDT for this enterprise, but I don't see anything against the nLite license for this if the user is informed and is given the copy of the disc used to build his or her machine (because if the user calls MS for assistance with that install, they're going to be told to reinstall with a clean XP disc and repro the problem before MS will help them, for starters).

If you're trying to get a dump of the system (which you should be), use those steps. The tools aren't necessary for that, just the system changes and a reboot.

The file you uploaded is corrupted. The forum can cause this with binary files renamed to TXT - PLEASE DO NOT RENAME .DMP FILES BEFORE UPLOADING thankyouverymuch . If you want us to take a look, please upload it again, unmolested.

Yes, I got that from your first post. Have you tried another FTP client to make sure it's not a client-side issue? Otherwise, you'd have to ask GoDaddy for their take on this.

Have you even considered my previous post? A driver issue it may be, but it sounds like kernel memory exhaustion to me (caused by a driver, likely, of course). Get some .dmp files of it crashing so we can see - preferably full dumps.

If you're using the site to zone assignment list, this would be expected behavior (the list looking empty, and getting an error when adding - not the zone issues themselves). If you need to add a list, and you want users to be able to edit them afterwards, you want to use an IE Maintenance policy in preference mode (or add the sites via a .reg or reg add commands on login). As to a site in one zone showing in another, there are ways to see what's happening. Send me a PM Monday morning if you haven't gone on vacation and I'll see if I can help you out with that - urlmon can be traced to see which zone, and why.

MSFT is a solid blue-chip stock, and even the large numbers don't compare to Apple's profit per sale - Microsoft sells far more units of product compared to Apple, but Apple's markup is far higher so they make more profit per sale. Given their main market is still the consumer space, and consumers are still buying new revs of every product it seems with each release cycle, Apple will probably be able to grow their cash cushion similar to the way MS did in the 90s due to strong sales. The problem for Apple will be if there is a real challenger in the consumer space to the iPhone or iPad, and Android (or even WP7, although I see that as more of an enterprise device with consumer capabilities, and will likely sell well in that space ahead of Crackberries) might be that contender. If Apple loses a good chunk of sales in the phone space, they still have the iPod and the iPad, although that would cause a pretty decent hit to profits YoY. I don't see it happening this year, and maybe not even the next, though, so I expect holding Apple stock for the next 12 - 24 months to be well worth it. Microsoft stock is good for your retirement fund, stocks like Google and Apple (if you got in early enough) are good for increasing your net worth before you retire .

Depends on the server in use at the time - CuteFTP can only create filenames the FTP server supports, so unless the FTP server supports uploads with filenames of this type, you are out of luck. I'd ping the host and see what options they have for doing this - you can't be the only one trying to do this.

Option 252 is for WPAD, which is a jscript language script that browsers can run (and you're somewhat limited in functions that can run as wpad scripts). These are also only parsed as proxy routing scripts - it's not something you can "force" the client to run at any other time, plus the browser in question must support running proxy pac scripts assigned via WPAD (not all can, although most major browsers do). Option 252 will not work for what you want it to, not to mention the WPAD script won't be requested until the first time the browser needs it, when making it's first request for a site. To do this, you're going to need to create your own option, and write a program that can use the data passed down via that option - option 252 is a well-known option, and really only works as I mentioned above. You *could* potentially use it, but you're likely to break web browsing using a browser that checks option 252 if you do, so I wouldn't recommend it.

There are no drivers specifically for Server 2008 R2, because it's Windows 7 underneath. A Win7 driver will work fine on Server 2008 R2 (besides, usually the server is the server, and not the client ). Coffee's link is the link to the Win7 basic driver set for that printer though (and I don't remember who asked before, but drivers for this specific printer were linked here on MSFN somewhere recently from the same type of question). As to shrinking, the print job itself is usually formatted by the app doing the printing, not the driver. However, the driver *is* responsible for telling the app the paper size, so if the printer is reporting the wrong size, that would be a driver issue.

Group policy works, but you won't be using applocker. You'll be limited to what UAC/LUA affords running as a non-admin user. The user will be able to install user-installable apps (like google chrome, or firefox), unless you use something 3rd party to restrict installations (or resort to software restriction policies in group policy, which is a heck of a lot more complicated... but easier to circumvent by smarter users... go figure).

I'd remove the new one and test the old one with memtest86+, as many passes as you can stand. Then I'd do the same with the old one. Assuming you get to a point where both pass, I'd run without the old one for awhile and see what happens.

If you've got access to DaRT, you could always create an ERD and scan it from there after downloading the latest defs during the creation of the ERD.

For Office 2003, only Office Processional Enterprise editions are licensed to create and deploy from administrative installation points, that is correct. I believe your MAPS gives you the Professional version, and not Professional Enterprise. Also, it did go into extended support in April of 2009, but it's still "supported". It's just not going to get any bugfixes or design changes, only security fixes (until 2014).

Well, this seems pretty random to me: // Trap frame showing the reason for the bugcheck: 1: kd> .trap 0xffffffff980669a0 ErrCode = 00000002 eax=fe484008 ebx=00000001 ecx=fe4843d4 edx=fe4840f0 esi=00732691 edi=fe484070 eip=92ccad63 esp=98066a14 ebp=98066cd4 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 win32k!xxxUserProcessCallout+0xe9: 92ccad63 007409ff add byte ptr [ecx+ecx-1],dh ds:0023:fc9087a7=?? // The thread is in IE, trying to write to GDI via win32k.sys: 1: kd> !thread THREAD 866f97e8 Cid 0b34.0b5c Teb: 7ffd9000 Win32Thread: fe51c008 RUNNING on processor 1 Not impersonating DeviceMap 978ae870 Owning Process 866f0860 Image: iexplore.exe Attached Process N/A Image: N/A Wait Start TickCount 26616 Ticks: 0 Context Switch Count 18648 UserTime 00:00:19.875 KernelTime 00:00:09.656 Win32 Start Address iertutil!CIsoScope::RegisterThread (0x7681407f) Stack Init 98066fe0 Current 98066ce0 Base 98067000 Limit 98064000 Call 42c Priority 11 BasePriority 8 PriorityDecrement 2 IoPriority 2 PagePriority 5 ChildEBP RetAddr Args to Child 98066988 81a56dd4 00000001 fc9087a7 00000000 nt!MmAccessFault+0x10a 98066988 92ccad63 00000001 fc9087a7 00000000 nt!KiTrap0E+0xdc (FPO: [0,0] TrapFrame @ 980669a0) 98066cd4 92c7a9bf a1010979 00000199 0000013d win32k!xxxUserProcessCallout+0xe9 (FPO: [2,3,4]) 98066d30 81a53c7a a1010979 00000199 0000013d win32k!NtGdiLineTo+0x64 (FPO: [3,17,4]) 98066d30 77a25e74 a1010979 00000199 0000013d nt!KiFastCallEntry+0x12a (FPO: [0,3] TrapFrame @ 98066d44) 029e8828 7797c6ae 7797c696 a1010979 00000199 ntdll!KiFastSystemCallRet (FPO: [0,0,0]) 029e882c 7797c696 a1010979 00000199 0000013d GDI32!NtGdiLineTo+0xc (FPO: [3,0,0]) 029e884c 6cf62a8f a1010979 00000199 0000013d GDI32!LineTo+0x92 (FPO: [3,0,4]) 029e887c 6cf6cb1d 00000000 029e88f0 029e8bd0 mshtml!XHDC::LineTo+0x5e 029e88d4 6cf64b33 00000000 0a6ca610 00000000 mshtml!DrawSimpleBorder+0x298 029e8bb0 6cf648ab 029ed3d0 029ed3c0 0a6ca610 mshtml!DrawBorder+0x2055 029e8bf4 6cedd21d 029ed360 029ed3c0 029e8c70 mshtml!DrawBorder+0x38 029e8cd8 6cf6291c 029e8d18 029e8d28 0a6ca610 mshtml!CDisplayBox::DrawClientBorder+0x1e1 029e8d38 6ce286e4 003e89d0 029e8e64 0aad3058 mshtml!CDispNode::DrawBorder+0xed 029e8f04 6ce28e7f 003e89d0 09a6b078 00000007 mshtml!CDispContainer::DrawSelf+0x15f 029e9050 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029e9078 6cedc7fd 003e89d0 029e9308 003e89d0 mshtml!CDispContainer::DrawChildren+0x56 029e9128 6ce294c8 09a6b024 003e89d0 029e91d0 mshtml!CDispContainer::DrawContentAdvanced+0x9b 029e92fc 6ce28e7f 003e89d0 09a6b024 00000007 mshtml!CDispContainer::DrawSelf+0x2b4 029e9448 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029e9470 6cede25e 003e89d0 029e95c8 00040000 mshtml!CDispContainer::DrawChildren+0x56 029e95bc 6cede0cf 003e89d0 0a9da258 00000007 mshtml!CDispContainer::DrawChildrenInActiveLayer+0x7e 029e9708 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x207 029e9730 6cede25e 003e89d0 029e9888 00040000 mshtml!CDispContainer::DrawChildren+0x56 029e987c 6cede0cf 003e89d0 0aa4ef70 00000007 mshtml!CDispContainer::DrawChildrenInActiveLayer+0x7e 029e99c8 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x207 029e99f0 6cedc7fd 003e89d0 029e9c80 003e89d0 mshtml!CDispContainer::DrawChildren+0x56 029e9aa0 6ce294c8 0acd03b4 003e89d0 029e9b48 mshtml!CDispContainer::DrawContentAdvanced+0x9b 029e9c74 6ce28e7f 003e89d0 0acd03b4 00000007 mshtml!CDispContainer::DrawSelf+0x2b4 029e9dc0 6cede42a 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029e9dec 6ce28e7f 003e89d0 00000000 00000007 mshtml!CDispProxyNode::DrawSelf+0x7b 029e9f38 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029e9f60 6cede27e 003e89d0 029ea1f0 003e89d0 mshtml!CDispContainer::DrawChildren+0x56 029ea010 6ce294c8 0a7e6000 003e89d0 029ea0b8 mshtml!CDispContainer::DrawContentAdvanced+0xb5 029ea1e4 6ce28e7f 003e89d0 0a883d48 00000007 mshtml!CDispContainer::DrawSelf+0x2b4 029ea330 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029ea358 6ce2952e 003e89d0 029ea528 00000000 mshtml!CDispContainer::DrawChildren+0x56 029ea51c 6ce28e7f 003e89d0 0a7bef28 00000007 mshtml!CDispContainer::DrawSelf+0x28a 029ea668 6ce2959e 00000000 003e89d0 00000000 mshtml!CDispNode::Draw+0x217 029ea690 6ce2952e 003e89d0 029ea860 00000000 mshtml!CDispContainer::DrawChildren+0x56 // Disassembly: 1: kd> u 92ccad63 win32k!xxxUserProcessCallout+0xe9: 92ccad63 007409ff add byte ptr [ecx+ecx-1],dh 92ccad67 7604 jbe win32k!xxxUserProcessCallout+0xf3 (92ccad6d) 92ccad69 57 push edi 92ccad6a e8216bffff call win32k!DestroyCacheDC (92cc1890) 92ccad6f 3b37 cmp esi,dword ptr [edi] 92ccad71 7502 jne win32k!xxxUserProcessCallout+0xfb (92ccad75) 92ccad73 8bfe mov edi,esi 92ccad75 8b37 mov esi,dword ptr [edi] // Looking at registers to get the PTE: 1: kd> r Last set context: eax=fe484008 ebx=00000001 ecx=fe4843d4 edx=fe4840f0 esi=00732691 edi=fe484070 eip=92ccad63 esp=98066a14 ebp=98066cd4 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 win32k!xxxUserProcessCallout+0xe9: 92ccad63 007409ff add byte ptr [ecx+ecx-1],dh ds:0023:fc9087a7=?? // The PTE contains nothing - this is bad: 1: kd> !pte fc9087a7 VA fc9087a7 PDE at 00000000C0603F20 PTE at 00000000C07E4840 contains 0000000000000000 // The pool allocation behind this is corrupt, either because pool is corrupt or the pointer is wrong: 1: kd> !pool fc9087a7 Pool page fc9087a7 region is Unknown fc908000 is not a valid large pool allocation, checking large session pool... fc908000 is freed (or corrupt) pool Bad allocation size @fc908000, too large 1: kd> !poolval fc908000 Pool page fc908000 region is Unknown Validating Pool headers for pool page: fc908000 Pool page [ fc908000 ] is __inVALID. Honestly, at this point, your system memory is indeed suspect - either you have the buggiest install of Vista I've ever heard of (not likely), or you've got bad hardware underneath (these two at the least are in no way related, at all).

It's older

#1, violation of rule 13. #2, not in any way located in the right part of the forum. #3, new user, 1st post rule violation. 3 strikes, you're out. [banned].

Given this only happens when stressing the system, and the fact that you mentioned you don't see a problem otherwise, I'm going to ponder a bit about the system being out of enough nonpaged pool memory to handle the requests coming from drivers on the machine, most notably the video card driver. This is a minidump, which isn't going to show me anything about the memory pools in kernel, but the only time you should see a bugcheck like this is filesystem corruption (chkdsk /f) or when out of nonpaged pool during system stress.

That depends - if you load the machine with the same software, maybe, but maybe not. And if it is a hardware problem, then no for sure. I'd upload the latest one from just awhile ago - that will be fine.

It never is - it's really the holy grail of enterprise computing, and it's very difficult to do effectively. Also, while the edition is termed professional, it's meant for home office/small businesses who don't have volume licensing, and who would be less likely to be locking down Windows that way. Applocker+Group Policy is considered an enterprise feature, which comes with the Enterprise version of the OS meant for medium to large enterprises (and Ultimate, of course). It stinks, but that's how the editions are hashed out.