Software Distribution Network Access Account Issue

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Software Distribution Network Access Account Issue

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Microsoft Systems Management Server >> SMS 2003 >> Software Distribution Network Access Account Issue

Page: [1]

Message

<< Older Topic Newer Topic >>

Software Distribution Network Access Account Issue - 5/7/2008 10:09:17 AM

mp115

Posts: 274
Score: 7
Joined: 3/23/2005
Status: offline

Here's a little background... a couple of months back, my company let go a high level (enterprise admin) network analyst and as a result, we had to do an emergency password change on EVERY domain admin service account we used, including the one I use for SMS software distribution. Once I changed the password on my service account, I rebuilt every boot-CD ISO we had out there.

Ever since that password change, I've been having a sporadic problem on some, but not all secondary site servers and within each site server, on some, but not all image packages where the field tech that's using the SMS boot CD's to reimage with are getting an error on boot-up, before the menu ever displays, about an "...invalid login/password...". In doing some testing on my own local secondary site server, I had 2 machines (an XP and a 2000) that I was reimaging simultaneously from a boot-CD copy that came from the same ISO. The XP reimaged just fine, but the 2000 came up with the same failed login/password error before the image selection screen ever came up, so it must be at the point where it's trying to access the distribution point package folder.

I know the Software Distribution domain account gets imbedded in the boot-CD so it can use that account to access the image package folder. That's easy enough, but what, if anything, gets imbedded in an image package? I didn't think anything did, but when one image package succeeds and the other fails using the same boot-CD, it makes me think that something is associated with the image packages, or somewhere inbetween. I think I'm stumped. I've never come across any good detailed documentation on how this whole process works as far as what gets imbedded where, but if you have some you could point me to, that would be great.

< Message edited by mp115 -- 5/7/2008 10:12:12 AM >