Skip to main content

SCCM 2007 install

Seems to have a lot of dependencies!

Installing on a bare-bones 2008 x64 VM, and it requires:

- Schema extensions (warning)
- WSUS SDK on site server (warning) (needs WSUS, IIS (app/web), .net 3.0, SQL 2008 SP2, Report Viewer 2005
- MS Remote Differential Compression library registered (Features)
- SQL server sysadmin rights (needed to add the current user to the SQL installation with sysadmin permisson)
- SMS provider communication
- IIS not running (Features)
- BITS installed/enabled (Features)
- WebDAV installed/enabled (

Update: Finally able to finish this. After the debacle with Microsoft and AD replication, it's working great so far. I'll be looking at building the Office2007 package this afternoon.
( Refs here )

Update: Turns out if you don't extend the schema (we were hoping to avoid that), then it just doesn't work as it should. So we've extended the schema, rebooted, and we're trying again. Unfortunately the ccm.log file is not very descriptive, so it's hard to pin down why the client installs are not going through. At this point the ccmservice is installed on the client computers, but it doesn't stay running more than a second or so (by design, I figure), and no client install completes - I'm judging that by the control panel, which doesn't have the config options yet.

Well, the errors we've been seeing are HTTP (404, 500, 403, 405), and a webDAV error as well.

!--[LOG[Failed to correctly receive a WEBDAV HTTP request.]-->time="23:15:30.138+240" date="07-03-2009" component="ccmsetup" context="" type="3" thread="2312" file="ccmsetup.cpp:6064">

!--[LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 405)]-->

Dan opened up the IIS permissions, and we got as far as the aforementioned two errors, but that's it. The 405 error didn't seem to be in the IIS log.

We are at the point where installing this on a 2003 machine is looking tempting.

Hmmm..I installed WebDAV but didn't enable it. Now we're getting:

A new HTTP error. 401.

More errors, but different!

More IIS fiddling...

It was missing a virtual directory to point to, and even though IIS users were allowed, wasn't working, so we allowed everyone.

Dan also had to change the client.msi to an application...not 100% sure about that one.

Client install worked, but client/server cannot see each other. Turns out the site was not published (under site management), in either DNS, AD or anything. It has been published now, so we'll see how long this takes.

Update: Well, the pushing to clients failed on a bunch of them, so we ended up just setting it up via the package manually. Not a complete failure, but still not as nice as I'd have liked it to be.

The lesson is: SCCM 2007 is COMPLICATED, and not an afternoon installation kind of product!!! Read through the technet articles more than once...print them out if need be!



Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…