Since SP1 Adv. to Legacy Client Fail

[Karactur]

I need a resolution to a puzzle I am having. I have recently upgraded to SMS2K3-SP1, and have found that all new advertisements to LEGACY clients are failing, stating "Network" problems. It seems the Legacy clients no longer see the DP. This is only a factor with packages POST Sp1. Anything that was created PRE SP1 still run fine.

I have gone back to creating "Simple" batch packages with the same failure results. I was hoping someone has come across this, and there is a solution, or a log that I have yet to find that points to the issue.

I have gone so far as to setup a share to allow guest access, but the LEGACY client still cannot find the package.

I need a hand here. Thanks.

 

[Karactur]

Lets Update:

I have found that Advertisements ARE working, HOWEVER, its the Software Updates that do not. When I try to deploy a Critical Update, the system fails, and reports back "Bad Environment". All the logs point to "Path not Found"

If I run the command manually at the client workstation, the Update will preceed, which rules out the idea that the client cannot see the source files.

 

[SLMHC]

i thought i read somewhere that in SP 1 the legacy client would be not supported.

I think it was during the install of SMS 2003 that it said this.

I could be wrong though...

thanks,

Dave

 

[tbrennans]

Usually before you see your bad environment in the log you will see :

<![LOG[IsNetResourceAccessible failed with error code 0x00000005]LOG

which means it either cant find this share or has insufficient rights

should look something like \\servername\smspkgd$

the client side log would make this too (cant find or access the share)

I'd look for that and see what you come up with.

 

[tbrennans]

actually 0x00000005 is always insufficient rights/access denied....

 

[Karactur]

I have found resolution to this issue.

When Software updates creates a package, the admin defines the location to store the package, and I assumed this was to be the final shared location, BUT OOOOOOO NOOOOOOO, it STILL created another sms shared package, not in the regular location on the DP, .\smspkgd$ (It has 2 Drives,C;D) but in the .\smspkgc$. I had removed share rights to this share awhile back, since it was not in use. This time, it was.

I did find the clue in the SMSAPM32.Log on the client. The share was inaccessible. Funny how I never saw that line before until I stared at the logs for 5 hours!

Thanks for the advice as well to all, tbrennans was prob the closest match to the resolution.

SMS = "Simply Madening Software"

 

[ADQRIP]

i had a brainstorming about this with an out sourcing, you have to be sure that your clients have actualced client with sp1, if a client doesn´t you will have this problem

if you got a legacy client in one advance pc when you deploy the sp1 it will damage the client