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 (http://www.iis.net/downloads/default.aspx?tabid=34&g=6&i=1621)

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!

Sheesh.

Comments

Post a Comment

Popular posts from this blog

Learning through failure - a keyboard creation journey

Image
tl;dr Built a custom keyboard cuz I have weirdo nerve pain issues.   Learned a lot cuz I failed a lot.   Maybe 'do it right the first time' is a bad frame of mind.   The keyboard ended up being kinda nifty.   It has lights, and a trackball, and QMK, and it helps my issues.   \o/ ( tl;dr is internet lingo that means, too long; didn't read ) Pain as a key ingredient An old proverb says, 'necessity is the mother of invention', and that is how this story begins. Over the last few years, age or stress or something has caught up with me and I developed the need to change my human-to-computer interface.  Mousing changed to trackballing.  The traditional keyboard was swapped out for an ergonomic, and then split keyboard.  Complicated multi-finger-and-hand key combinations were replaced by single keypress macros.  And yet more was still needed. It's often said that change only happens with pain - indeed, the organizations many of us work in seem to apply this as law - an
Read more

Learning Opportunities - Watching/listening list

Over the last year I've spent a lot of time learning (thank you, long commute & lunch hours).  Many topics ranging from Chef to DevOps to architecture concepts to management concepts and everything in between.  Why have I done this? DevOps Demystified with Ben Rockwood: https://www.youtube.com/watch?v=h5E--QSBVBY DevOps at ancestry.com: https://www.youtube.com/watch?v=pF5ya0q53kk Those two presentations were key in sending me down this road.  First, and most important, was Mr. Rockwood's explanation as to the real 'why', and the point behind DevOps from an operational perspective.  Second, and no less important but for a different reason, the continuous delivery system at ancestry.com really made it real to me because they are a 'Windows shop'.  So much of what I'd been reading about Chef/config mgmt. relied on amazing tools (see the error there?) only available to the Linux world.  Suddenly here's this guy telling me that it's possible on
Read more

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 configured You see the DFSR folders get created on the other end, but nothing stages Finally 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$\user.name\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-99A
Read more