RE: OSD - Network Access Account Issue
- From: MikeP <MikeP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 May 2008 03:49:01 -0700
I did check the package folder permissions and went to so far as to add the
Everyone group with Read permissions on both the share and physical folder,
but it didn't seem to have an impact. It's like the login/password are saved
in either the boot-CD or the package reference on the boot-CD. Very strange
indeed. Prior to the password change, that account always had permissions to
these same folders.
I'll start digging around for that hotfix to see if I can find it. Thanks
for the heads up on that. I'm still running SP3. Did that hotfix get
influded in R2? If so, it might be time to bump it up to the last version.
"Sherry Kissinger [MVP-SMS]" wrote:
I'm not the OSD person at my company, but based on the log, it looks like.
that account may not have rights to the folder
\\TRFCSEC.MYDOMAIN.NET\SMSPKGD$\0000016B. Have you manually checked that the
account has NTFS rights to that folder? If you discover that it doesn't, in
the SMS console, for that Package, look at "Access Accounts". Compare it to
one that does connect; perhaps a group or user is missing? If Access
Accounts looks right, but the NTFS rights aren't on the folder, I recall
there was a hotfix about those access rights not being sent successfully
under SMS2003 in some cases... my (faulty) memory wants to say it was a
hotfix specifically for DPs that were grandchildren of the originating site,
but don't trust my memory on that point.
--
Standarize. Simplify. Automate.
"MikeP" wrote:
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 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.
The OSDInstallWizard.log file is showing the error, so it's something that's
stuck somewhere that's still being added to the boot-CD ISO files. I pasted
an exerpt from the log below.
-------------------------------------
Starting installation wizard. OSDInstallWizard 5/8/2008 1:42:42 PM 1196
(0x04AC)
Loading X:\i386\system32\RIPInfo.ini OSDInstallWizard 5/8/2008 1:42:42
PM 1196 (0x04AC)
Wizard title: Generic Images OSDInstallWizard 5/8/2008 1:42:42 PM 1196
(0x04AC)
Number of images available = 15 OSDInstallWizard 5/8/2008 1:42:42 PM 1196
(0x04AC)
Local user can NOT specify image location OSDInstallWizard 5/8/2008 1:42:42
PM 1196 (0x04AC)
Local user may specify computer name OSDInstallWizard 5/8/2008 1:42:42
PM 1196 (0x04AC)
Shared environment successfully initialized OSDInstallWizard 5/8/2008
1:42:42 PM 1196 (0x04AC)
Server Name : \\TRFCSEC.MYDOMAIN.NET, Client Name : \\MININT-GDQ51PSK,
Username = smssvcacct OSDInstallWizard 5/8/2008 1:42:42 PM 1196 (0x04AC)
A system error has occurred: 5 OSDInstallWizard 5/8/2008 1:42:42 PM 1196
(0x04AC)
Failed to connect to \\TRFCSEC.MYDOMAIN.NET\SMSPKGD$\0000016B. Invalid
username or password. OSDInstallWizard 5/8/2008 1:42:43 PM 1196 (0x04AC)
Client status handler is not available. No status will be
sent. OSDInstallWizard 5/8/2008 1:42:43 PM 1196 (0x04AC)
Failed to send status message C0002B61 (80070002) OSDInstallWizard 5/8/2008
1:42:43 PM 1196 (0x04AC)
Failed to unregister OSD environment object
(80070005) OSDInstallWizard 5/8/2008 1:42:43 PM 1196 (0x04AC)
The operating system installation failed. Please contact your system
administrator for assistance.
Could not connect to the installation package on
\\TRFCSEC.MYDOMAIN.NET\SMSPKGD$\0000016B. Logon failure: unknown user name or
bad password. (8007052E)
This message will automatically close in 30
minutes. OSDInstallWizard 5/8/2008 1:42:43 PM 1196 (0x04AC)
-------------------------------------
- References:
- OSD - Network Access Account Issue
- From: MikeP
- RE: OSD - Network Access Account Issue
- From: Sherry Kissinger [MVP-SMS]
- OSD - Network Access Account Issue
- Prev by Date: RE: VISTA SP1 on SMS 2003 SP3
- Next by Date: Re: SCCM Client Installation
- Previous by thread: RE: OSD - Network Access Account Issue
- Next by thread: AD Discovery
- Index(es):
Relevant Pages
|