Re: User based assignments not working when logged on via Remote Desktop (bug ?)

From: Shehzad Khoja [MSFT] (srkhoja_at_online.microsoft.com)
Date: 11/25/04


Date: Thu, 25 Nov 2004 12:57:27 -0800

Yes, SMS user SENS service to detect network change, user logged on or
logged on events. If this service is not running then SMS will not get those
notifications.

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"xs4all" <Flores@wissen.eken.nl> wrote in message 
news:41a5d16b$0$34762$e4fe514c@news.xs4all.nl...
> Yes... TS is not in anyway involved...
> I checked if the SENS service is running and it is... (I guess I would be 
> having more trouble if it wasn't ?)
>
> So enabled debuglogging and this is the result:
> <![LOG[Requesting User policy assignments for 
> 'S-1-5-21-99487913-3505896268-722186236-8829']LOG]!><time="12:47:43.782+-60" 
> date="11-25-2004" component="PolicyAgent_RequestAssignments" context="" 
> type="1" thread="3356" file="requestassignmentstask.cpp:1360">
> <![LOG[Requesting policy from authority 
> 'SMS:S01']LOG]!><time="12:47:43.891+-60" date="11-25-2004" 
> component="PolicyAgent_RequestAssignments" context="" type="1" 
> thread="3356" file="requestassignmentstask.cpp:1416">
> <![LOG[WTSQueryUserToken[2](SessionID=0) failed with 
> GLE=1723]LOG]!><time="12:47:43.907+-60" date="11-25-2004" 
> component="PolicyAgent_RequestAssignments" context="" type="1" 
> thread="3356" file="usertoken.cpp:1076">
> <![LOG[WTSQueryUserToken[2](SessionID=0) failed with 
> GLE=1723]LOG]!><time="12:47:44.406+-60" date="11-25-2004" 
> component="PolicyAgent_RequestAssignments" context="" type="1" 
> thread="3356" file="usertoken.cpp:1076">
> <![LOG[WTSQueryUserToken[2](SessionID=0) failed with 
> GLE=1723]LOG]!><time="12:47:44.904+-60" date="11-25-2004" 
> component="PolicyAgent_RequestAssignments" context="" type="1" 
> thread="3356" file="usertoken.cpp:1076">
> <![LOG[Aborting request. User is not logged on 
> anymore.]LOG]!><time="12:47:45.403+-60" date="11-25-2004" 
> component="PolicyAgent_RequestAssignments" context="" type="1" 
> thread="3356" file="requestassignmentstask.cpp:713">
>
> I guess the SessionID=0 is not correct here...
> Will try to exclude the user and machine from any policies today... 
> anymore suggestions in the meantime ?
>
> Regards,
>
> Flores Eken
>
>
> "Shehzad Khoja [MSFT]" <srkhoja@online.microsoft.com> wrote in message 
> news:uyW4Slk0EHA.1196@TK2MSFTNGP15.phx.gbl...
>> SMS only supports user logging on to WinStation0. This is that RD does. 
>> So it should work as long as you are using RD and logging on to console 
>> session. If you are using TS sessions then this would be an expected 
>> behavior.
>>
>> Since you are not using TS, can you enable verbose and debug logging and 
>> try to run this scenario again?
>> Also can you please make sure that Sens service is running. Anything 
>> special about the domain or group policy settings that you can think off?
>>
>> -- 
>> This posting is provided "AS IS" with no warranties, and confers no 
>> rights.
>>
>>
>> "xs4all" <Flores@wissen.eken.nl> wrote in message 
>> news:41a44741$0$78772$e4fe514c@news.xs4all.nl...
>>> Hi All,
>>>
>>> I have the following setup:
>>>
>>> SMS 2003 SP1 on Windows 2000 Server SP3
>>> Windows XP clients SP1 + all hotfixes and SMS Advanced Client
>>>
>>> All my software is is assigned to AD usergroups and users can install 
>>> software based on their AD group membership in Add/Remove programs.
>>> When a user is logged on via the console everthing works like a charm. 
>>> By selecting a program software can be installed.
>>>
>>> However, when the same user on the same workstation logs on via remote 
>>> desktop no software can be installed.
>>> All advertisments are listed in add/remove programs, but they cannot be 
>>> installed. Message: This program is not available right now.
>>>
>>> In the log files it is clearly visable that the advanced client is 
>>> having trouble determining the currently logged on user when using 
>>> remote desktop. This is a reproducable problem. Seems like a bug to 
>>> me... anyone suggestions ?
>>>
>>> Notice the "not logged on anymore" log statement..... offcourse this is 
>>> not true..
>>>
>>> Log (Remote Desktop)
>>> <![LOG[Requesting User policy assignments for 
>>> 'S-1-5-21-1220945662-1606980848-839522115-1115']LOG]!><time="14:31:13.842+-120" 
>>> date="10-01-2004" component="PolicyAgent_RequestAssignments" context="" 
>>> type="1" thread="3672" file="requestassignmentstask.cpp:1360">
>>> <![LOG[Requesting policy from authority 
>>> 'SMS:S01']LOG]!><time="14:31:19.794+-120" date="10-01-2004" 
>>> component="PolicyAgent_RequestAssignments" context="" type="1" 
>>> thread="3672" file="requestassignmentstask.cpp:1416">
>>> <![LOG[Aborting request. User is not logged on 
>>> anymore.]LOG]!><time="14:31:21.294+-120" date="10-01-2004" 
>>> component="PolicyAgent_RequestAssignments" context="" type="1" 
>>> thread="3672" file="requestassignmentstask.cpp:713">
>>>
>>>
>>> Log (Console)
>>> <![LOG[Requesting User policy assignments for 
>>> 'S-1-5-21-1220945662-1606980848-839522115-1115']LOG]!><time="14:48:00.779+-120" 
>>> date="10-01-2004" component="PolicyAgent_RequestAssignments" context="" 
>>> type="1" thread="700" file="requestassignmentstask.cpp:1346">
>>> <![LOG[Requesting policy from authority 
>>> 'SMS:S01']LOG]!><time="14:48:00.940+-120" date="10-01-2004" 
>>> component="PolicyAgent_RequestAssignments" context="" type="1" 
>>> thread="700" file="requestassignmentstask.cpp:1402">
>>> <![LOG[Raising event:
>>>
>>> instance of CCM_PolicyAgent_AssignmentsRequested
>>> {
>>> AuthorityName = "SMS:S01";
>>> ClientID = "GUID:B4350360-936B-4251-B980-40CC94CA5316";
>>> DateTime = "20041001124801.050000+000";
>>> ProcessID = 1648;
>>> ResourceName = "S-1-5-21-1220945662-1606980848-839522115-1115";
>>> ResourceType = "User";
>>> ThreadID = 700;
>>> };
>>> ]LOG]!><time="14:48:01.050+-120" date="10-01-2004" 
>>> component="PolicyAgent_RequestAssignments" context="" type="1" 
>>> thread="700" file="event.cpp:522">
>>>
>>>
>>> Regards,
>>>
>>> Flores Eken
>>>
>>
>>
>
> 


Relevant Pages

  • Re: User based assignments not working when logged on via Remote Desktop (bug ?)
    ... SMS is getting this error from terminal services when it is ... I am not sure in which all circumstances, Terminal services would return ... >>> All my software is is assigned to AD usergroups and users can install ... >>> software based on their AD group membership in Add/Remove programs. ...
    (microsoft.public.sms.swdist)
  • RE: error 53: The network path was not found
    ... child domain names in as a DNS suffix on the SMS server. ... I am not sure of what you man by "throttling the discovery back". ... Refer to the discovery logs for more information. ... still getting these errors with no agent install. ...
    (microsoft.public.sms.setup)
  • Re: Office 2007 Deployment
    ... Other than the SMS restarts it's identical I ... first time start up issues if the computer reboots after install) ... attempt at the command line from SCCM didn't. ... What if you manually uninstall Office 2003 then try running SMS ...
    (microsoft.public.sms.admin)
  • Re: Distribution Problem FAILED
    ... Objective of SMS is deploying the software ... ... If so then provide that switch in the command line. ... >> this program to install silently without any user interaction. ... >>>>> did not click the advertised program icon appear, ...
    (microsoft.public.sms.swdist)
  • Re: error 53: The network path was not found
    ... all computers are members of the same child domain but the SMS ... SMS Active Directory System Group Discovery Agent reported errors for 615 ... still getting these errors with no agent install. ... (“Can you install client manually successfully? ...
    (microsoft.public.sms.setup)