Answered by:
Issue with installing SCCM client to Direct Access workstations

Question
-
I have about 1,500 Direct access clients and having trouble installing the SCCM client. I created a startup script GPO using Jason Sandy's script (http://blog.configmgrftw.com/configmgr-client-startup-script/)The DA client attempts to install but continue to receive error Failed to get client version for sending messages to FSP. Error 0x8004100e . I have tried several client installation switches to attempt to install. I have tried
ccmsetup.exe /mp:SCCMServer.domain.com SMSSITECODE=XX FSP=SCCMServer.domain.com
ccmsetup.exe /mp:SCCMServer.domain.com /service SMSSITECODE=XX FSP=SCCMServer.domain.com
Here are the logs:
Running on platform X64 ccmsetup 5/13/2015 7:40:42 AM 4608 (0x1200)
Updated security on object C:\windows\ccmsetup\cache\. ccmsetup 5/13/2015 7:40:42 AM 4608 (0x1200)
Launch from folder C:\windows\ccmsetup\ ccmsetup 5/13/2015 7:40:42 AM 4608 (0x1200)
CcmSetup version: 5.0.7958.1000 ccmsetup 5/13/2015 7:40:42 AM 4608 (0x1200)
In ServiceMain ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Successfully started the ccmsetup service ccmsetup 5/13/2015 7:40:42 AM 5672 (0x1628)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/13/2015 7:40:42 AM 5672 (0x1628)
CcmSetup is exiting with return code 0 ccmsetup 5/13/2015 7:40:42 AM 5672 (0x1628)
Running on 'Microsoft Windows 7 Enterprise ' (6.1.7601). Service Pack (1.0). SuiteMask = 272. Product Type = 18 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Ccmsetup command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice "/mp:SCCMServer.domain.com" "/BITSPriority:LOW" "SMSSITECODE=XX" "FSP=SCCMServer.domain.com" ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Command line: "C:\windows\ccmsetup\ccmsetup.exe" /runservice "/mp:SCCMServer.domain.com" "/BITSPriority:LOW" "SMSSITECODE=XX" "FSP=SCCMServer.domain.com" ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
SslState value: 224 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
CCMHTTPPORT: 80 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
CCMHTTPSPORT: 443 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
CCMHTTPSSTATE: 224 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
CCMHTTPSCERTNAME: ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
FSP: SCCMServer.domain.com ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
CCMFIRSTCERT: 1 ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Config file: ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Retry time: 10 minute(s) ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
MSI log file: C:\windows\ccmsetup\Logs\client.msi.log ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
MSI properties: SMSSITECODE="XX" FSP="SCCMServer.domain.com" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Source List: ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
MPs: ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
SCCMServer.domain.com ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
No version of the client is currently detected. ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Folder 'Microsoft\Configuration Manager' not found. Task does not exist. ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Updated security on object C:\windows\ccmsetup\. ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Sending Fallback Status Point message to 'SCCMServer.domain.com', STATEID='100'. ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
Params to send FSP message '5.0.7958.1000 Deployment ' ccmsetup 5/13/2015 7:40:42 AM 2460 (0x099C)
State message with TopicType 800 and TopicId {FED66794-B990-468A-9373-F080C9FA7CCD} has been sent to the FSP FSPStateMessage 5/13/2015 7:40:42 AM 2460 (0x099C)
Running as user "SYSTEM" ccmsetup 5/13/2015 7:40:43 AM 2460 (0x099C)
Sending Fallback Status Point message to 'SCCMServer.domain.com', STATEID='328'. ccmsetup 5/13/2015 7:40:43 AM 2460 (0x099C)
Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 5/13/2015 7:40:43 AM 2460 (0x099C)
Params to send FSP message '5.0.7958.1000 Deployment Error 0x80004005' ccmsetup 5/13/2015 7:40:43 AM 2460 (0x099C)
State message with TopicType 800 and TopicId {901F6969-5D6C-48BD-93CC-2841D27B1B7F} has been sent to the FSP FSPStateMessage 5/13/2015 7:40:43 AM 2460 (0x099C)
CcmSetup failed with error code 0x80004005 ccmsetup 5/13/2015 7:40:43 AM 4608 (0x1200)Wednesday, May 13, 2015 1:13 PM
Answers
-
That snippet of log is not very helpful. Have you created a boundary for the Direct Access clients (it will need to be IPv6 Prefix)? You need to add this boundary to a Boundary Group.
Tip: to get the IPv6 Prefix execute the following PoSH command on the Remote Access server
Get-RemoteAccess | select ClientIPv6Prefix
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, May 13, 2015 1:57 PM -
I don't think there was PoSH support for this on W2008. Have a look at this. It tells you how IPv6 Prefix was configured in the Remote Access console. You may be able to find it there
http://blog.pluralsight.com/server-2008-directaccess-configuration
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, May 13, 2015 4:04 PM
All replies
-
That snippet of log is not very helpful. Have you created a boundary for the Direct Access clients (it will need to be IPv6 Prefix)? You need to add this boundary to a Boundary Group.
Tip: to get the IPv6 Prefix execute the following PoSH command on the Remote Access server
Get-RemoteAccess | select ClientIPv6Prefix
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, May 13, 2015 1:57 PM -
Thanks Gerry. Do you know how I can get the Remote Access powershell cmdlets? Will I have to install the Direct Access Management Console?
Wednesday, May 13, 2015 3:48 PM -
We are using Server 2008 Direct Access. BTWWednesday, May 13, 2015 3:50 PM
-
I imagine these cmdlets are available on the Direct Access access server itself?Wednesday, May 13, 2015 3:54 PM
-
All I see here is that the powershell features are enabled with a feature install on the server:
https://technet.microsoft.com/en-us/library/jj574200.aspx
Wednesday, May 13, 2015 3:56 PM -
I have tried to run the cmdlets on the Direct Access server. However, I get the objectnotfound. I don't know much about Direct Access so I apologize for my ignorance.
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.PS C:\Users\test> get-remoteaccess
The term 'get-remoteaccess' is not recognized as the name of a cmdlet, function, script file, or operable program. Chec
k the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:17
+ get-remoteaccess <<<<
+ CategoryInfo : ObjectNotFound: (get-remoteaccess:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundExceptionWednesday, May 13, 2015 3:57 PM -
I don't think there was PoSH support for this on W2008. Have a look at this. It tells you how IPv6 Prefix was configured in the Remote Access console. You may be able to find it there
http://blog.pluralsight.com/server-2008-directaccess-configuration
Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson
Wednesday, May 13, 2015 4:04 PM