Please note, your reply will need to be approved by a moderator before it is posted in the forum.

Reply to 'Notify.vbs + SCCM + Remote Database doesn't work' in Intel® vPro™ Expert Center

This helps prevent automated registrations.
This helps prevent automated registrations.
Attach Files Max Size: 15.0 MB , All file types allowed
 

Replying To:

Notify.vbs + SCCM + Remote Database doesn't work
ricdanger Community Member

Hi,

 

I'm trying to get the new host based configuration to work with SCCM, but the provided notify.vbs script doesn't seem to work when the site database is not hosted on the configuration manager server. As far as I can see, Notify.vbs blindly adds the sccmSiteServer address as the SQL server:

 

'Invoke string with arugments for SiteCode,SQLServer Name,
'Resource Name (FQDN of AMT machine),
'ResourceID returned from ImportComputers
'This code uses the translator to work around and SCCM AMT import bug

strInput="<p:ImportComputer_INPUT xmlns:p=""ImportWizard"">" &_
          "<p:Site>" & "SMS_" & sitecode & "</p:Site>" &_
          "<p:Server>" & sccmSiteServer & "</p:Server>" &_
          "<p:Name>" & fqdn & "</p:Name>" &_
          "<p:ResourceId>" & ResourceID & "</p:ResourceId>" &_
          "</p:ImportComputer_INPUT>"

 

But changing it to my real database server does not seem to work, because wsman translator tries to connect using named pipes (should try TCP for remote database). I had a look at the wstrans source but didn't find any reference to SQL.

 

Any idea how to fix this?

 

Thanks.

Think of a tag as a simple category name. You can categorize your documents, discussions, and blog posts with any word or words that makes sense.
Suggested Category