we are seeing a few issues relating to SCCM SP0 client talking to SCCM SP2 backend.
These are related to running task sequences.
Two issues at the moment are:
+ 183 error when trying to start a task sequence on a 64 bit client. This seems to be related to having more than one TS advertised to the client, the even ones get the 183 error
+ on 'some' machines, command line tasks in TS's which are called from a referenced 'package' (e.g. the tickbox in the command line options page) the running command line cannot get access to shell variables, e.g. %computername% etc are blank. we have only seen this on SCCM Server clients though
These are related to running task sequences.
Two issues at the moment are:
+ 183 error when trying to start a task sequence on a 64 bit client. This seems to be related to having more than one TS advertised to the client, the even ones get the 183 error
+ on 'some' machines, command line tasks in TS's which are called from a referenced 'package' (e.g. the tickbox in the command line options page) the running command line cannot get access to shell variables, e.g. %computername% etc are blank. we have only seen this on SCCM Server clients though
