using vNext in a LAB - Part 4. Configuring the Client Agent Settings

[anyweb]

In Part 1. of this series we Installed vNext.

In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. In Part 3, we installed the Reporting Point Role along with some additional roles and configured them.

 

Now we will configure the Client Agents and install the client on our Lab systems.

 

Perform the following on the vNext server as SMSadmin

 

Step 1. Configure Default Settings for the Computer Agent

 

In the vNext console, click on Administration, and then right click on Client Agent Settings choose Modify Default Settings.

 

 

Scroll down to Computer Agent and select Organization Name, change it to your organisation name

 

 

While we are there let's add the default software catalog website to trusted sites zone, double click on it and change false to true

 

 

and let's select the default software catalog web site point, double click on it and change the drop down menu to VNEXT

 

 

Click Ok when done.

 

At this point you can startup Internet Explorer and browse to your Vnext Software Catalog Web Site Point http://vnext/CMSoftwareCatalog/

 

[anyweb]

Step 2. Configure Client Installation Settings

 

In the Administration node of the Wunderbar click on Site Operations, Sites and select our vNext site V01, select Client Installation Settings in the bottom right.

 

 

Double Click on Client Push Installation to set its' settings and then click on the Accounts Tab. Click on the yellow starburst to add a new account

 

 

 

we will use the following user created in AD in part 1 of this series, ClientInstall (a domain admin user in this lab, the screenshot below is from the Active Directory server)

 

 

After clicking on the yellow starburst, add your ClientInstall details

 

 

Click on the Client tab and add FSP=VNEXT to add the Fallback Status Point properties to our client installation settings.

 

 

Click Apply then ok to exit.

[anyweb]

Step 3. Install the Client

 

In the Wunderbar, select Assets and Compliance and select the All Systems collection.

 

 

In this lab we will select all our systems (ctrl_a) and choose Install Client from the Actions menu,

 

 

the Client Push Installation Wizard appears, click next

 

 

Select the Include Domain controllers option (to Install the client on AD1) and click next

 

 

review the summary

 

 

click Next and view the completion results

 

 

Troubleshooting Tip:

 

You can open Task Manager on one of the computers that you are installing the client on, look for CCMSETUP.EXE starting/running

 

 

After some minutes the clients will be installed, Check the All Desktops and Servers collection, you should see your computers listed with Client = Yes

 

[Stijn]

Very nice tutorial.

But if I configure CMSoftwareCatalog and go the webpage I get this:

 

System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60129.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60129.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60129.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)

at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClass5.<EndGetResponse>b__4(Object sendState)

at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__1(Object sendState)

--- End of inner exception stack trace ---

at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)

at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)

--- End of inner exception stack trace ---

at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)

at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)

at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

at System.ServiceModel.ClientBase`1.ChannelBase`1.EndInvoke(String methodName, Object[] args, IAsyncResult result)

at Microsoft.ConfigurationManagement.ServicePortal.PortalControls.ServiceReference.ApplicationViewServiceSoapClient.ApplicationViewServiceSoapClientChannel.EndGetApplicationValuesForProperty(IAsyncResult result)

at Microsoft.ConfigurationManagement.ServicePortal.PortalControls.ServiceReference.ApplicationViewServiceSoapClient.Microsoft.ConfigurationManagement.ServicePortal.PortalControls.ServiceReference.ApplicationViewServiceSoap.EndGetApplicationValuesForProperty(IAsyncResult result)

at Microsoft.ConfigurationManagement.ServicePortal.PortalControls.ServiceReference.ApplicationViewServiceSoapClient.EndGetApplicationValuesForProperty(IAsyncResult result)

at Microsoft.ConfigurationManagement.ServicePortal.PortalControls.ServiceReference.ApplicationViewServiceSoapClient.OnEndGetApplicationValuesForProperty(IAsyncResult result)

at System.ServiceModel.ClientBase`1.OnAsyncCallCompleted(IAsyncResult result)