client side targeting doesn´t work!

Thu, 11 Jun 2009 07:34:51 Z

hello,

it´s me again.

i have some problmes with the so called "client side targeting".
i hope you can help me.

all of my devices are stored in the part unassigned devices although i enable the option client side targeting.
Furthermore from my point of view the policy is correct.

of courese it is possible to disable "client side targeting" and "throw" the devices manually in th right group!

can you please help me?!

thanks and best regards!

client side targeting doesn´t work!

Thu, 11 Jun 2009 10:37:55 Z

Client side targeting works really well. You need to add your WSUS container name in the Group Policy, and configure WSUS. Don't forget to change the WSUS options. Right Click on "Devices" in the Software distribution console and select Options. Choose the Group Policy option. This should get Client Side Targeting working.

You need to manually create the containers within the Software Distribution Console. The group policy Target Group Name needs to match these containers exactly.
You can specify multiple containers in the Target Group Name field e.g. "default;Executive"

Cheers Wayne
Airloom

client side targeting doesn´t work!

Fri, 12 Jun 2009 07:35:49 Z

thanks for your answer!

i already know how i have to configure my wsus distribution service and of course i did the same you told me.

a little bit strange is when i try to enroll new devices these devices will appear in the right wsus group but there round about ten devices which are in the unassigned part.

furthermore there are another problem because 600% of my devices don´t appear anywhere. the devices are not in the unassigned part or in my created parts. where can i find these devices?

Another problem ist that 30% of my devices show me the "error message" this devices has not reported status in 60 or more days"
why? my connect now tool shows me a success connection?????

thanks
best regards
ameo!

client side targeting doesn´t work!

Sun, 14 Jun 2009 21:45:26 Z

The connect now tool will connect to the MDM server for updated policies etc. I don't believe this will verify your connection to WSUS.

You also mention that your devices don't appear anywhere. This is probably because they have not contacted WSUS yet, You should be able to find these devices in Active Directory Users and Computers under the Managed Devices container (Assuming that's where they go by default. )

client side targeting doesn´t work!

Mon, 15 Jun 2009 00:46:45 Z

Ameo,

How have you configured your Device OU's in AD. Do you have multiple OU's for different business units ? If you have your devices distributed between different OU's, are the "missing" device from one specific OU ?
If you are using the "SCMDM Managed Devices (Instance)" OU for all your devices, then it might be device specific.
What device makes/models are you using ? Are the specific "missing" devices the same make/model ?

When you add a new device does it show up ?

Cheers Wayne
Airloom

client side targeting doesn´t work!

Mon, 15 Jun 2009 05:46:25 Z

hi,

many thanks for your answers!!!

How have you configured your Device OU's in AD. Do you have multiple OU's for different business units ? If you have your devices distributed between different OU's, are the "missing" device from one specific OU?

yes of course we have multiple OU's for different business units but there are no devices missing from one specific OU but there are missing devices in every OU!
sorry, david creedy is right. i can all devices find in the AD but not in the wsus console of my mdm server.

If you are using the "SCMDM Managed Devices (Instance)" OU for all your devices, then it might be device specific.

What exactly is the SCMDM Managed Devices (Instance)??

What device makes/models are you using ? Are the specific "missing" devices the same make/model ?

we "only" use one specific devices in fact it is the htc ameo 16gm version.

When you add a new device does it show up ?

when i now enroll new devices which appeaer automatically in the right wsus group and of courese in the ad.
but whats about the other 60% of my devices which are not shown? the devices are already shared in the country and used form our field worker.
do you know a special powershell command which maybe will start a kind of scan progress for the wsus console?!

thanks and best regrads!
ameo

client side targeting doesn´t work!

Mon, 15 Jun 2009 07:03:20 Z

Ameo,

What exactly is the SCMDM Managed Devices (Instance)??

thanks and best regrads!
ameo

This is the default container for your SCMDM SP1 device. Are you running SP1 ? If the Instance name is "Contoso" then the container would be "SCMDM Managed Devices (Contoso)".

Make sure the devices are getting to the Device Management Server for Policy update. To check whether the devices are getting policy updates - Open the MDM Admin Console -> All Managed Devices. Sort by "Last Connected". Are the missing devices showing up as connected recently?

Even though the device do not show up in Software Distribution Console, have you tried deploying software to these devices? I have seen the console only update while software is being deployed.

Cheers Wayne
Airloom

client side targeting doesn´t work!

Mon, 15 Jun 2009 09:42:41 Z

thanks for the fast answer!

we dont use sp 1.

the missing devices are shown in the mdm console an the connection status is up to date. but, i already said this, the devices don´t appear in the distribution group!

Even though the device do not show up in Software Distribution Console, have you tried deploying software to these devices? I have seen the console only update while software is being deployed.

i ´didn´t try to enroll software but i will try it!

there are no possibility to start a kind of new inventory process for the distribution service?!

THANKS!

client side targeting doesn´t work!

Wed, 17 Jun 2009 15:26:23 Z

nobody can help me?!

when i delete some mobile devices from the wsus console which are enrolled for round about 4 weeks these mobile devices will appear automatically in the wsus console after 10 minutes.

but for round about 4 month we had to reinstall the wsus or other worded the software distribution service of mdm and all devices which were available before the reinstall are lost since now!

only new enrolled devices will appear in the wsus console and of course you can delete these devices and these devices will appear again automatically.

but whats about the old devices which were enrolled before the reinstall of our software distribution service????
are there any possible to add these devices in the wsus console????

thanks!

client side targeting doesn´t work!

Sun, 21 Jun 2009 11:58:04 Z

nobody can help me?!

client side targeting doesn´t work!

Mon, 22 Jun 2009 01:48:34 Z

This is happening to a few people posting in the forum. It seems that certain devices fail to register with Software Distribution, but it seems random.
Install the Device Status Viewer on one of the devices that is having an issue and enable Logging. Select "Enable Alerter Log" and select "Software Distribution".
Post the output.

Cheers Wayne
Airloom

client side targeting doesn´t work!

Thu, 25 Jun 2009 07:53:24 Z

iam very sorry but where can i find the log files?

i turned on the device status viewer and enable logging but in /application data/logs there are no log files???

thanks!

client side targeting doesn´t work!

Sat, 27 Jun 2009 13:57:31 Z

nobody can tell me where i can find the log files of the Device Status Viewer?

client side targeting doesn´t work!

Sun, 28 Jun 2009 23:49:32 Z

Ameo,

NodeMon log - If this option is checked, the system generates a log file at \NodeCache.txt
OMADM log - If this option is checked, the system generates a log file at \deviceupdate.log
Software Distribution - If this option is checked, the system generates a log file at \deviceupdate.log

Cheers Wayne
Airloom

client side targeting doesn´t work!

Wed, 01 Jul 2009 14:32:40 Z

@
waynephillips

thanks!

from my point of view the disservicemanager.exe is responsible for the software distribution, or?

here are the log information:

2009-06-29 16:04:14 disservicemanager.exe:+WinMain: lpCmdLine=

2009-06-29 16:04:15 disservicemanager.exe:+-CBaseWnd::CBaseWnd

2009-06-29 16:04:15 disservicemanager.exe:+-CBaseCmdWnd::CBaseCmdWnd

2009-06-29 16:04:15 disservicemanager.exe:+CBaseCmdWnd::OnInitServiceManager

2009-06-29 16:04:15 disservicemanager.exe:+CServiceManager::CServiceManager

2009-06-29 16:04:15 disservicemanager.exe:-CServiceManager::CServiceManager

2009-06-29 16:04:15 disservicemanager.exe:+CServiceManager::ActivateAllServices

2009-06-29 16:04:15 disservicemanager.exe:+CServiceManager::OpenServiceRootKey

2009-06-29 16:04:15 disservicemanager.exe:-CServiceManager::OpenServiceRootKey:hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+CBaseService::ActivateService

2009-06-29 16:04:15 disservicemanager.exe:+ISL_Init

2009-06-29 16:04:15 disservicemanager.exe:+CInstallService::Init

2009-06-29 16:04:15 disservicemanager.exe:-CInstallService::Init: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+CInstallService::Start

2009-06-29 16:04:15 disservicemanager.exe:+CInstallService::ServiceThread

2009-06-29 16:04:15 disservicemanager.exe:-CInstallService::Start: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+CInstallService::CheckRebootPendingJobs

2009-06-29 16:04:15 disservicemanager.exe:-ISL_Init : hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:Error: CInstallQueue:FindFirst: hr=0x80070103

2009-06-29 16:04:15 disservicemanager.exe:-CBaseService::ActivateService: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+-DisFreeInstallJobInfo

2009-06-29 16:04:15 disservicemanager.exe:+CBaseService::Start

2009-06-29 16:04:15 disservicemanager.exe:-CInstallService::CheckRebootPendingJobs: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+ISL_IOControl: dwCode=0x1040004

2009-06-29 16:04:15 disservicemanager.exe:+SendMsgToServiceManager: uMsg=1333 wServiceBitPattern=0x2

2009-06-29 16:04:15 disservicemanager.exe:+CInstallService::Start

2009-06-29 16:04:15 disservicemanager.exe:-CInstallService::Start: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:-ISL_IOControl: g_dwState=1, fReturn=1, hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+CBaseService::Start : fReturn=1

2009-06-29 16:04:15 disservicemanager.exe:+CBaseService::ActivateService

2009-06-29 16:04:15 disservicemanager.exe:+UIS_Init

2009-06-29 16:04:15 disservicemanager.exe:+CUIService::Init

2009-06-29 16:04:15 disservicemanager.exe:-CUIService::Init: hr=0x1

2009-06-29 16:04:15 disservicemanager.exe:-UIS_Init : hr=0x1

2009-06-29 16:04:15 disservicemanager.exe:-CBaseService::ActivateService: hr=0x0

2009-06-29 16:04:15 disservicemanager.exe:+CBaseService::Start

2009-06-29 16:04:15 disservicemanager.exe:+UIS_IOControl: dwCode=0x1040004

2009-06-29 16:04:16 disservicemanager.exe:+CUIService::Start

2009-06-29 16:04:16 disservicemanager.exe:+CUIService::WorkerThread

2009-06-29 16:04:16 disservicemanager.exe:+CUIService::LoadUIModule

2009-06-29 16:04:16 disservicemanager.exe:+CUIService::GetUIGuid

2009-06-29 16:04:16 disservicemanager.exe:CDownloadMgrUI::CDownloadMgrUI

2009-06-29 16:04:16 disservicemanager.exe:+CDownloadMgrUI::Initialize

2009-06-29 16:04:16 disservicemanager.exe:+CDownloadMgrUI::__MessagePump

2009-06-29 16:04:16 disservicemanager.exe:+-CDUEllipseText::CDUEllipseText

2009-06-29 16:04:16 disservicemanager.exe:+CStatusDialog::OnInitDialog

2009-06-29 16:04:16 disservicemanager.exe:+CStatusDialog::SetUpFont

2009-06-29 16:04:16 disservicemanager.exe:-CStatusDialog::SetUpFont, hr=0x0

2009-06-29 16:04:16 disservicemanager.exe:+CDUEllipseText::Init

2009-06-29 16:04:16 disservicemanager.exe:-CDUEllipseText::Init: hr=0x0

2009-06-29 16:04:16 disservicemanager.exe:+DisListenForDownloadStatusEvents

2009-06-29 16:04:16 disservicemanager.exe:+CUIServiceHandler::CreateUIServiceHandler

2009-06-29 16:04:16 disservicemanager.exe:+-CUIServiceHandler::CUIServiceHandler

2009-06-29 16:04:16 disservicemanager.exe:+CUIServiceHandler::Initialize

2009-06-29 16:04:16 disservicemanager.exe:-CUIServiceHandler::Initialize: hr = 0x0

2009-06-29 16:04:16 disservicemanager.exe:+CUIServiceHandler::__WorkerThread

2009-06-29 16:04:16 disservicemanager.exe:-CUIServiceHandler::CreateUIServiceHandler: hr = 0x0

2009-06-29 16:04:16 disservicemanager.exe:+CUIServiceHandler::WorkerThread

but i don´t see any big error messages

thanks!

client side targeting doesn´t work!

Tue, 14 Jul 2009 03:50:40 Z

The log doesn't contain anything that would indicate the cause of the problem.

Cheers Wayne
Airloom

client side targeting doesn´t work!

Thu, 16 Jul 2009 22:22:17 Z

yes, i already guessed this.

but the whole log file din´t contain any erros in respect of software distribution. so what can i do?!

is the only solution for this problem a new enrollment for each device?!
that would be horrible....

thanks!

client side targeting doesn´t work!

Wed, 22 Jul 2009 04:33:53 Z

Try turning on Logging on your DNS server. I had one instance where the device was trying to contact "update.windowsmobileupdate.com" for software distribution. Check you DNS server for strange DNS queries coming from the VPN IP Pool.

Cheers Wayne
Airloom