astx813

Yes, these are non-mandatory advertisements, I have to press F12 once for "Network Service Boot." Why, though, does it put me through the abortpxe thing when I try to PXE boot again after a successful task sequence? I don't see any duplicates in the All Systems collection. I guess if I can fix problem 1, this will no longer be an issue, then. The software advertisement was also not mandatory. I will look to the logs. Since there are about 40 log files, are there any you'd recommend checking before the others? Thanks

I think I remember seeing a thread once that detailed a list of reasons to run the site database on the primary SCCM server, but I haven't been able to find it. I've been thinking back to that recently, as I've got several small issues plaguing my pre-production environment. There are a few reasons I suspect a database issue: Clearing PXE Advertisements - There have been a few threads about sometimes being unable to "Clear Last PXE Advertisement," but in my system, we've never been able to. The Clear PXE Advertisement window says "there are no items to show in this view" every time. Yes, I've waited to make sure it's not just taking a moment to run the query. Removing/updating collection memberships - As a result of being unable to clear the advertisements, I've resorted to deleting and re-adding computers, but this too behaves oddly. I would delete a computer, then "Import single computer" (via Computer Association), but the newly imported machine wouldn't show up in any collections. The only way I've been able to get back up & running is to create a direct membership rule and do a search for the machine name I just deleted. Advertisements not showing on clients - After I deploy an OS, none of the software advertisements appear on the client's Run Advertised Programs control panel. What say you, are these all symptoms of a database problem, or are these actually three independent problems? The current database is SQL Server 2005 running on Server 2003 x64.

Some high priority and optional updates aren't showing up in my Update Repository. The high priority updates are KB973687 and KB967715. In the SUP Component Properties, I enabled All Classifications (speaking of which, how do I purge the drivers from the list after I uncheck that category?), I enabled the Windows XP product, and I performed a synchronization. I created a Search Folder for all XP updates, and I checked the automatically-generated Updates folder, the updates aren't in either. I'm at a loss at this point, would be grateful for any advice. Once I get these two figured out, I'll worry about the optional ones. FWIW, those updates are both titled "Update for Windows XP." One has to do with excessive HTTP requests with a "well-known DTD," the other fixes something with autorun not being disabled properly.

All I saw in your post was the suggestion to add exceptions for ports 2701-2702, which I mentioned I had done. And FWIW, the client is Windows 7.

As it says in the topic, I'm unable to remote control my client PCs using Start -> Remote Tools in the ConfigMgr console. I have narrowed it down to a firewall issue, and I made headway, but haven't had success yet. I know it is a firewall problem, because was able to connect when I disabled it. I re-enabled it and started poking holes, but haven't gotten through. I did manage to go from "Unable to contact host," to "Connection failed (0x8000ffff)." Per the Windows TechNet entry Windows Firewall Settings for Configuration Manager Clients, I allowed the following: TCP port 135 open to the admin subnet TCP ports 2701-2702 open to IPs in my admin subnet The program C:\Windows\SysWOW64\RCAgent.exe Allowed Remote Desktop connections (via System Properties control panel) I believe it was after opening port 135 that I started getting 0x8000ffff. Anyone know what I'm leaving out? Thanks.

FIXED! It took me a while to pick up on this one, but I found the source of the problem! "The specified service does not exist..." had me thinking this wasn't about just a missing script. I took a close look at the contents of the TS and the scripts that were being called, because I couldn't figure out why this was the only mention of bddrun.exe in the logs, despite the fact that this was just another "Run Command Line" step in the TS. The problem was that I was being very security minded when I set this all up, and I wasn't willing to give Everyone full control over my Deployment Share, so I had used the "run this step as the following account" so the Create WIM stage could use an account with permissions. And that was the problem, I guess BDDRUN doesn't work in WinPE or something. Disabling that and giving write permissions to Everyone got it working. Sure hope someone can learn from my mistake! Now, let's see what I get stuck on next...

Using a basic setup of MDT & WDS, I've created a simple task just to deploy and capture a base Windows 7 image. It deploys just fine, but fails during the capture phase. Testing via command prompt showed that it wasn't a permission issue (no trouble at all writing to the specified capture share). I took a look through the SMSTS.log and this was the first thing to catch my attention Executing command line: %TOOLROOT%\bddrun.exe /runas cscript.exe "%SCRIPTROOT%\ZTIBackup.wsf" TSManager 1/7/2011 5:09:43 PM 1584 (0x0630) Process completed with exit code 1060 TSManager 1/7/2011 5:09:43 PM 1584 (0x0630) Failed to run the action: Create WIM. The specified service does not exist as an installed service. (Error: 00000424; Source: Windows) TSManager 1/7/2011 5:09:43 PM 1584 (0x0630) I happened to notice that there is no ZTIBackup script to be found. There are plenty of scripts in <Target Drive>\MININT\Scripts and in <Boot Drive>\Deploy\Scripts, but ZTIBackup.wsf isn't one of them. Any idea why this file is missing? I have a hunch this is the source of my current headache. This task sequence is just a "Standard Client Task Sequence" that does nothing more than install the OS and Firefox. Thoughts? Ideas? This wasn't the source of my headaches. I injected the missing script into the WIM and I'm still getting the same errors. Oh, the headaches...

*Insert obligatory statement of praise for anyweb and the rest of the community here* Having followed the guides and picked my way through various pitfalls, errors, and failures, I am now stuck. At first I thought it was a network driver issue, but I've added the drivers, the card is detected, and I can ping the SCCM server by name. A little before the half-way point in the logs, are a series of entries Attempting to connect to "\\DEPLOY.LAW.VIRTUAL\SMSPXEIMAGES$\SMSPKG\LAB00006". Retrying download... It says this 10 times, then errors with "Failed to connect..." The SMSPXEIMAGES$ share was automatically created, so I don't know how the permissions could be wrong in it. But if someone can tell me what they *should be* then I can verify they're set right. The next series of errors comes at the end of the log, with the lines Failed to save environment to (80070057) Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base <snip> Would the line "We do not find an available volume to store the local data path" (8 lines up from this failure) have any connection with this? I do have an accessible local drive, I can access it using DISKPART. Finally, where it seems to come crashing down, in the OSDNetSettings.exe section Failed to read installation type from environment.. Please ensure you are running this executable inside a properly confiured OS Deployment task sequence. Unspecified error (Error: 800004005; Source: Windows) Guessing this has to be the SMSPXEIMAGES$ permissions... On the one hand, yeah, it's a permissions issue. I gave Everyone read access to the folder and it successfully connected to LAB00006... And yet that hasn't changed the outcome. I'm still getting all the other errors. Thoughts? Thanks, and Happy New Year! smsts-chipsets.log