tomwrz

You're not alone. I can slipstream SP2 no problem. The process for slipstreaming the hotfixes goes fine too, but when I run a scan against the system, after the installation, it still shows that all the same hotfixes are applicable. I'd love to find an answer to what's going on.

This is strange issue and there's not much out there on the web about it...may someone here can help. Randomly, when a user sends an email with multiple attachments, the user on the receiving end will get the email with attachments but... the names of some or all of the attachments have swapped names with the other attachment within the same email. Let me give you an example...I can send an email with doc1, doc2, and doc3 attached. The user on the other end will see all three attachments. However, when they open doc1 it is actually doc2...doc2 is actally doc3 or doc1. What's crazy is that this can even happen with different file extensions...if doc1 is a Word document and pdf1 is an Adobe document they can, and have, switched file names. So when the user opened the Word document, it was actually the PDF and vice versa. Now, if you save the documents and change the extensions, everything is fine. Like I said, this is completely random and we cannot reproduce the problem with any given user. A user may call with the problem, our Help Desk contacts them and cannot recreate the problem...a couple of days or weeks go by and user may call again. Personally, I believe that there is an issue on the Exchange side, but I need to do all of the troubleshooting that I can from the client. But hopefully someone has seen this issue and knows of a fix. Any help will be appreciated.

This is strange issue and there's not much out there on the web about it...may someone here can help. Randomly, when a user sends an email with multiple attachments, the user on the receiving end will get the email with attachments but... the names of some or all of the attachments have swapped names with the other attachment within the same email. Let me give you an example...I can send an email with doc1, doc2, and doc3 attached. The user on the other end will see all three attachments. However, when they open doc1 it is actually doc2...doc2 is actally doc3 or doc1. What's crazy is that this can even happen with different file extensions...if doc1 is a Word document and pdf1 is an Adobe document they can, and have, switched file names. So when the user opened the Word document, it was actually the PDF and vice versa. Now, if you save the documents and change the extensions, everything is fine. Like I said, this is completely random and we cannot reproduce the problem with any given user. A user may call with the problem, our Help Desk contacts them and cannot recreate the problem...a couple of days or weeks go by and user may call again. Personally, I believe that there is an issue on the Exchange side, but I need to do all of the troubleshooting that I can from the client. But hopefully someone has seen this issue and knows of a fix. Any help will be appreciated.

Thanks for the replies! I have finally (after several months now) found the exact answer to my problem. Here it is: If I installed the unattended XP on a GX240,260 or whatever it would show as Uniprocessor. So I figured that if these HALs were the same it should work without a problem. I found that by just changing the HAL to ACPI Multiprocessor PC the next system would simply blue screen. I then found that by adding a [sysprep] section in the sysprep.inf with BuildMassStorageSection = Yes along with another section [sysprepMassStorage], the problem with one image on multiple machines was resolved. By adding those sections the [sysprepMassStorage] is automatically filled during the sysprep process. So if you to are having this issue with the unattended install...make sure it is set to ACPI Multiprocessor PC and add to two sections above to your sysprep.inf. Also, you can add the following to your winnt.sif file to force the system to use the Multiprocessor HAL during the unatteded install: [unattended] UpdateHAL = MPS_MP,%windir%\inf\hal.inf

In our environment we have an image that works for muliple machines: Dell GX240,260,270,280,520. There's nothing special that we did to make this work...we built it from the ground up (installed XP then drivers then apps). So what's different with the unattended installation that doesn't allow me to use one image on different machines? The unattended install that I have works perfect on every machine that I mentioned above, but if I were to image, say a GX260 after the install, it will not work on any other machine but the GX260. Common answers that I've seen are: "this can't be done", "change the HAL". There are many related discussions about this, but none mention that they already have this working as we do without using the unattended process. If I take the image of any of the computers above, stick it in another machine and run a repair everything works fine...but I can't take that image and place it back in the original computer and have it work without running another repair. So basically, what happens differently during the unattended install that may cause this to happen. Again, this process of one image for different machines works fine if built from the ground up on any one of the above machines. Thanks in advance for any help