Should I move the database role back to my primary SCCM box?

[astx813]

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:

1. 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.
   
2. 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.
   
3. 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.

[daniz]

1. Are you using non-mandatory OS advertisements? If you are pressing F12 two times to enter the installations there is no PXE advertisement to clear. If you are using mandatory advertisements and you can't clear it I have to agree it is strange. I have seen strange behavior if you have duplicate objects, some beeing obsolete, but then you simple have to clear all of the objects with the same name. Remember to update All systems collection to make sure you are seeing any duplicate objects.

 

2. I find removing and then re-adding computer objects and adding them to a collection in the wizard is a bit buggy, so I think this behavior is "normal".

 

3. If you are using mandatory advertisements they are not going to show in the run advertised programs. If you are using non mandatory advertisements i have to agree it is strange but start by checking log files to make sure there is nothing wrong with boundarys and so on.

[astx813]

1. 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.
   
2. I guess if I can fix problem 1, this will no longer be an issue, then.
   
3. 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

[daniz]

1. To explain: you only need to clear a pxe boot when using mandatory advertisement. If you have the problem try restarting the WDS service of the PXE server. If it works it is the WDS PXE cache that is causing the problem.

 

http://www.myitforum.com/articles/1/view.asp?id=12603

http://blog.danovich.com.au/2010/03/23/windows-deployment-services-wds-cache/

 

If this is the problem make sure you change the correct registry key. The key is different for x64 and x86 versions of windows server.

 

2. Hopefully solved by 1.

 

3. I would start by looking at the client c:\windows\system32\ccm\logs\locationservices.log check so the client is in a defined site and so on.