Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??
From: Jim Bradbury [MSFT] (jimbrad_at_online.microsoft.com)
Date: 01/21/05
- Next message: Jim Bradbury [MSFT]: "Re: Stop publication on client"
- Previous message: JJ: "Re: Distrubution of Software Update"
- In reply to: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Next in thread: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Reply: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 20 Jan 2005 17:45:47 -0800
John,
I'm not looking at a site right now, but I checked the other SMS shares
yesterday and on my SMS 2003 SP1 site (on Windows 2003), all of the shares
that you indicated have Everyone with Full Control listed. However, I
didn't look closely at the file permissions.
Note: I don't recall the specific history of my site (one of many VPC
images), so this certainly isn't a definitive statement of the default
settings. Unfortunately, I couldn't find any current documentation
regarding the specific share and file permissions, which have changed a over
the course of various SMS Service Packs.
Since Shezahd has some different thoughts on the default SMS share
permissions, I should probably setup a clean SMS site before posting more
share/file permissions listings. I won't be able to setup a clean site
tomorrow (Friday), but I will try to get to it on Monday and post my
findings.
I'm glad that changing the package share permissions resolved your problem.
-- Thanks, Jim Bradbury This posting is provided AS IS with no warranties and confers no rights. "John Guderian" <lanadmin@avrinc.com> wrote in message news:unN65dy$EHA.3700@tk2msftngp13.phx.gbl... > SMS 2003 is installed on a Windows 2003 box, which as you stated has > default share permissions of Read to 'Everyone'. However after changing > the 'Everyone' permission to Full Control, everything started to work, > including the import of .pdf files, and .sms files. All the NTFS > permissions are the same. > > If SMS doesnt alter Share permissions, my existing share permission set of > Read Only would have worked. I havent changed any of the NTFS permissions. > > I would still like to verify the permissions that I have to ensure they > are correct, and that security is maintained. I have run the aclreset.exe > command in the past based off of a microsoft suggestion. > > Can you provide the share, and NTFS permissions so that I can verify what > I currently have? > > Thanks > > "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in message > news:%23S9Fy2x$EHA.2180@TK2MSFTNGP10.phx.gbl... >> SMS doesn't force any share permissions. By default, all shares are set >> to have full permissions for 'Everyone' on Win2k and Read to 'Everyone' >> on Win2k3. >> It is the NTFS permissions which actually contorl who gets what? >> >> -- >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> >> >> "John Guderian" <lanadmin@avrinc.com> wrote in message >> news:uwNxjjw$EHA.1264@TK2MSFTNGP12.phx.gbl... >>> Well simply changing the share permission on the SMSPKGD$ folder for the >>> everyone group to full control made all the difference. All of a sudden >>> my errors went away, and the package copied to the distribution point. I >>> decided to change all of the SMS share permissions to everyone full >>> control, and I can now import .pdf files as well which wasnt happening >>> before. >>> >>> However, would you mind verifying the exact share & file permissions for >>> the 5 SMS shares below? >>> >>> CAP_"site name" >>> SMS_"site name" >>> SMS_SITE >>> SMS_SUIAgent >>> SMSClient >>> >>> I appreciate your help! >>> >>> >>> "Jim Bradbury [MSFT]" <jimbrad@online.microsoft.com> wrote in message >>> news:eauPWan$EHA.2444@TK2MSFTNGP10.phx.gbl... >>>> As was suggested in a previous post, I would also suggest enabling NAL >>>> logging to get specific information on the error that is occurring. >>>> NAL logging is valid for both SMS 2.0 and SMS 2003, at least for this >>>> component. >>>> >>>> A quick glance at my SMS 2003 SP1 site shows: >>>> - Share permissions of Everyone at Full Control >>>> - File permissions of Administrators at Full Control and Guests and >>>> Users at Read & Execute. >>>> >>>> However, I can't remember whether this was an upgrade (2.0 -> 2003 >>>> RTM -> 2003 SP1) or a clean installation. >>>> >>>> Based on your earlier comment, I would suggest checking your share >>>> permissions (and enabling NAL logging). >>>> --- >>>> Thanks, >>>> Jim Bradbury >>>> This posting is provided AS IS with no warranties and confers no >>>> rights. >>>> >>>> "John Guderian" <lanadmin@avrinc.com> wrote in message >>>> news:ebC7bum$EHA.3820@TK2MSFTNGP11.phx.gbl... >>>>>I have an additionl thread below that seems to have been abandoned, >>>>>however my last response indicates where I left off. This post is dated >>>>>1/4/05. >>>>> >>>>> I am still running into issues with this error, and trying to import >>>>> .sms, or .pdf files do not work. >>>>> >>>>> Any help would be greatly appreciated. Currently the software >>>>> distribution feature is at a stand still. Is there any way to >>>>> re-install the distribution point to a default install if this cant be >>>>> fixed? >>>>> >>>>> Thanks >>>>> >>>> >>>> >>> >>> >> >> > >
- Next message: Jim Bradbury [MSFT]: "Re: Stop publication on client"
- Previous message: JJ: "Re: Distrubution of Software Update"
- In reply to: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Next in thread: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Reply: John Guderian: "Re: Additional suggestions for previous post "Distribution Manager error 2324 1/4/05"??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
