SMS Client - Temporary Program Download Folder settings

Discussion:

(too old to reply)

Seanuu

2010-03-16 15:06:01 UTC

SMS Client Version 2.50.4253.3000

Where does it get it's Temporary Program Download Folder settings from?

Hello all

I am having a problem with the Temporary Program Download Folder settings of
SMS Client Version 2.50.4253.3000.

We are currently testing using SMS in our organization. A couple of weeks
ago we moved to testing in a "real world" situation in one of the offices.

We tested on 7 machines. 5 worked perfectly.

We have traced the problem with the other two machines to the Temporary
Program Download Folder settings on the local SMS Client.

This is the folder to which SMS downloads the Package before running.

1.0 Correct Settings

On the machines that run OK, the settings point the location of this folder
to:

C:\WINDOWS\system32\CCM\Cache

with the amount of disk space to use as:

250 MB

2.0 Incorrect Settings

On the machines that do not run OK, the settings point the location to:

C:\WINNT\system32\CCM\Cache

with the amount of disk space to use as:

0 MB

and everything is greyed out with no ability to alter anything.

Other Details

All these machines are Windows XP and have C:\Windows as their windir
directory.

None of the machines have a C:\WINNT directory.

Because there is no WINNT directory, SMS cannot download the Package to run
it.

What we are now trying to find out is where the SMS Client picks up the
Temporary Program Download Folder settings from. If we can then alter the
details in that location, it should solve our problem.

Any help or suggestions would be much appreciated.

Sean

Sherry Kissinger [MVP]

2010-03-17 12:24:01 UTC

Permalink

This does not really answer your question, but if you are just now starting
to test SMS 2003 SP3... you do know that SMS 2003 is end of life?

You really need to start with System Center Configuration Manager 2007
(ConfigMgr 2007). It's already on SP2, Configmgr 07 has been out so long...

Post by Seanuu
SMS Client Version 2.50.4253.3000
Where does it get it's Temporary Program Download Folder settings from?
Hello all
I am having a problem with the Temporary Program Download Folder settings of
SMS Client Version 2.50.4253.3000.
We are currently testing using SMS in our organization. A couple of weeks
ago we moved to testing in a "real world" situation in one of the offices.
We tested on 7 machines. 5 worked perfectly.
We have traced the problem with the other two machines to the Temporary
Program Download Folder settings on the local SMS Client.
This is the folder to which SMS downloads the Package before running.
1.0 Correct Settings
On the machines that run OK, the settings point the location of this folder
C:\WINDOWS\system32\CCM\Cache
250 MB
2.0 Incorrect Settings
C:\WINNT\system32\CCM\Cache
0 MB
and everything is greyed out with no ability to alter anything.
Other Details
All these machines are Windows XP and have C:\Windows as their windir
directory.
None of the machines have a C:\WINNT directory.
Because there is no WINNT directory, SMS cannot download the Package to run
it.
What we are now trying to find out is where the SMS Client picks up the
Temporary Program Download Folder settings from. If we can then alter the
details in that location, it should solve our problem.
Any help or suggestions would be much appreciated.
Sean

Seanuu

2010-03-18 11:26:01 UTC

Permalink

Thank you for the reply Sherry.

Yes! We know this. We are supposed to be moving to SCCM "soon", but due to
the nature and size of our organization (and the the nature and size of our
department within that organization) we do not know when this move will take
place.

My particular section are therefore testing SMS:

1. In case the SCCM move is delayed even longer;

2. So we can learn and gain experience in concepts and techniques that will
be transferable to SCCM; and

3. To discover any possible problems we might have with the use of both
technologies.

I notice on several of the forums that there are many posts on questions
regarding moving from SMS to SCCM, and especially on upgrading the SMS Client
on PCs to the SCCM client.

I would love to believe that when we finally move over to SCCM our SMS
Client problem will just disappear, but I am a bit dubious.

In fact, that we already have this problem leads me to expect even more
problems during the SCCM move.

Though I hope not.

Thanks again for the reply.

Sean
--
Sean

Post by Sherry Kissinger [MVP]
This does not really answer your question, but if you are just now starting
to test SMS 2003 SP3... you do know that SMS 2003 is end of life?
You really need to start with System Center Configuration Manager 2007
(ConfigMgr 2007). It's already on SP2, Configmgr 07 has been out so long...

Seanuu

2010-03-25 16:28:01 UTC

Permalink

We now seem to have a solution to this SMS Client problem.

Basically:

On the local machine running the Client, the Registry entry for the PATH
details should be REG_EXPAND_SZ and not REG_SZ.

This Microsoft Knowledgebase article has the details of the problem and
instructions on how to change the Registry entry type:

http://support.microsoft.com/kb/922362

The relevant details are:

"Method 2: Set the type of the Path registry entry to REG_EXPAND_SZ

1. Click Start, click Run, type regedit, and then click OK.

2. In Registry Editor, locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment

3. Make sure that the type of the Path entry is REG_EXPAND_SZ and not
REG_SZ. If the type of this entry is REG_SZ, you must copy the path
information, delete the existing Path entry, and then create a new entry of
type REG_EXPAND_SZ."

We are now going to look at:

1. Trying to find a way to use SMS to query our machines to discover whether
they have the Client problem.

2. Trying to find a way to remotely change the Registry entry type on those
machines that have the problem.

Thanks for the help Sherry.

Sean