WNottsC
asked on
Why does SCCM client Temporary Program Download Folder change location
I have been having problems with SCCM for a while and think I have managed a solution to getting it installed, Automatic client push still will not work for some reason but I have a way of getting the client on and to start with it looks like they are working fine.
However after a while the Current location for the Temporary Program Download Folder on the clients changes from C:\WINDOWS\system32\CCM\Ca che to C:\WINNT\system32\CCM\cach e
and then seems to stop communicating. Can anyone explain this?
A little extra detail:
The servers seem to work fine and automatic push install works with them as well, they are on the same subnet as the SCCM server could this be the reason and if so how do I fix this.
The DHCP is on a different server to the SCCM and WDS in case this makes a difference and option 60, 66, and 67 need setting if so what should these be?
However after a while the Current location for the Temporary Program Download Folder on the clients changes from C:\WINDOWS\system32\CCM\Ca
and then seems to stop communicating. Can anyone explain this?
A little extra detail:
The servers seem to work fine and automatic push install works with them as well, they are on the same subnet as the SCCM server could this be the reason and if so how do I fix this.
The DHCP is on a different server to the SCCM and WDS in case this makes a difference and option 60, 66, and 67 need setting if so what should these be?
ASKER
this did not seem to make any difference where would it be picking the winNT from is it trying to get this from the server? On some machines it works fine with the %windows root% (or something like that) but on others it then reverts back after a couple of days to the winnt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Please upload the execmgr.log file
ASKER
hope this will explain where it is going wrong not much in it
execmgr.log
execmgr.log
From the log file it looks like the client is not installed properly (or not in a site boundary), can you upload the clientIDManagerStartup.log file and LocationServices.log file.
click Start, click Run, type sysdm.cpl
In the System Properties dialog box, click the Advanced tab, and then click
Environment Variables.
Under System Variables, click windir, and then click Edit.
Note You may have to move the scroll box next to the list to see this entry.
In the Variable value box, capitalize the first letter, and then click OK.
For example, change "c:\windows" to "C:\windows."
Click OK OK
Restart the computer to make sure that the new environment variable takes
effect.
Try this on single computer first, hopefully this will fix the issue