MDT Scripts, Front Ends, Web Services, and Utilities for use with ConfigMgr/SCCM

New Post: Treeview for GETOUs with MDT Wizard

brandonrcampbell — Wed, 22 May 2013 20:57:33 GMT

Has anyone or does anyone know how to create a treeview with option of GETOUs? I'm using the web service. Kind of figured out how to execute the web service and return the results... but can't figure out how to use a treeview control in the wizard pane. On top of that I wouldn't know where to start to get the xml data inside the treeview. Any insight would be great!

New Post: Move Computer to Staging OU script question

neosyfte — Wed, 22 May 2013 15:56:39 GMT

Thank you. I appreciate you taking time out.

New Post: Move Computer to Staging OU script question

tech3 — Wed, 22 May 2013 13:13:05 GMT

I am in a meeting for the next 4 hours but when I am done I will give you exactly what I did with screenshots and a walk through.

New Post: Move Computer to Staging OU script question

neosyfte — Wed, 22 May 2013 11:30:18 GMT

tech3,

I am having the same issue that you were having. However, I am a little confused on how you changed the conditions on the "MoveComputer" and "SwapOU" scripts. Would you mind sharing the changes you made? Perhaps a sample copy of the code.

Thanks.

New Post: SCCM.asmx/AddComputerToCollection: The operation timed out

Fred_Smith — Thu, 09 May 2013 17:16:45 GMT

Hi. I have Deployment Web service (v7.3) setup and running and have been using it since you released it without issues, even previous versions for a few years. Love them.

I have a few different task sequences advertised to several collections, all with unknown support. The problem I have and see from time to time, is that when the service SCCM.asmx/AddComputerToCollection runs to dump the system into the appropriate collection, what is being logged in my frontend script, is

Error executing web service http://SERVER/OSD_Deployment/SCCM.asmx/AddComputerToCollection: The operation timed out (-2147012894)
Unable to call AddComputerToCollection web service.

Then, what appears to happen is an “unknown” record is created in the site. What happens next is when the machine try’s to retrieve policy it is presented with all advertised task sequences, not just the one assigned to the collection selected.

Not sure why the webservice is timing out, I have looked in the iis.logs and see nothing but 200 returns. And there are no event log entries either.

Any suggestions or ideas?

New Comment on "Documentation"

quantumburnz — Thu, 02 May 2013 15:02:56 GMT

Hello -- What versions of SCCM is this compatible with? Does it work with SCCM 2012 and SP1? What you put together certainly sounds useful!

Created Issue: Query for DN not going against local DC [7383]

permster — Tue, 02 Apr 2013 23:07:36 GMT

I don't know if this issue impacts other function calls or not but I know for sure the MoveComputerToOU experiences this issue.

When looking over the log file it shows the MoveComputerToOU fuction call finding the local domain controller for the machine. Then it goes to look up the DN for the computer. This query doesn't go against the local domain controller and will fail if replication hasn't yet occured between the sites.

Since the function already knows the local domain controller the DN query should also be going against the local domain controller. This would resolve the issue.

Please also check to make sure this isn't an issue for any of the other functions that need to query the DN for an object.

New Post: Source code for the Webservice

ibauersachs — Tue, 19 Mar 2013 16:58:35 GMT

Hey

I've seen the other post were you've stated you're undecided whether to publish the source code or not. While I'd respect your decision, at the same time you don't have much of a choice as long as you're hosting this on CodePlex. This is a site for open source projects and as such the source code must be available:

What are the requirements for hosting a project on CodePlex?
Your project must meet the following criteria:

You must choose a license for your project (license resources: Open Source License page on Wikipedia)
It must be an ongoing project (no "abandoned" projects)
It must have source code (no non-software projects)

(From http://codeplex.codeplex.com/wikipage?title=Project%20hosting%20requirements)

So, please either publish the source code or remove the project from CodePlex.

Regards,
Ingo

New Post: Move Computer to Staging OU script question

tech3 — Thu, 14 Mar 2013 15:34:58 GMT

Thank you for the tip. It works exactly as you have it set up. That being said the issue that has now presented itself is that the move computer to stagingOU script is used to swap the values of my OU's which I still need. Regardless whether the machine is in AD or a new bare metal that has not yet been in AD the script still swaps the values. Otherwise the PC just joins to its finalOU instead of my staging OU that has no policies. (legal notices etc..) Does that make sense?

New Post: Move Computer to Staging OU script question

nolram — Wed, 13 Mar 2013 22:40:14 GMT

Use the executewebservice script and check for computerexistance, save to a property then make that a condition for that action to run:
Create a run command line task before the movecomputer task:

cscript.exe %ScriptRoot%\ZTI_ExecuteWebservice.wsf /wsSection:DoesComputerExist /wsProperty:PCExists /wsResultName:boolean

Then on the "MoveComputer" task right after it set the condition to "if all conditions are true" and "Task sequence variable PCExists equals true"

Dont forget to create the custom property PCExists.

In Custom Properties ini file:

[DoesComputerExist]
WebService=http://server:port/ad.asmx/DoesComputerExist
Parameters=HostName
HostName=ComputerName
PCExists=boolean

New Post: MoveComputerToOU using DC local to web service

ajdltd — Mon, 11 Mar 2013 13:48:32 GMT

We ended up putting a delay in the Task sequence to allow for replication and moved on

Andy Dawson

New Post: MoveComputerToOU using DC local to web service

permster — Fri, 08 Mar 2013 21:42:23 GMT

Was this issue ever resolved? I've experienced this exact same thing. The MoveComputerToOU function finds a local DC for computer but when it's trying to find the distinguished name of the computer and OU it goes against DC's local to the web service. It should be using the DC's local to the computer for the distinguished name lookup. This will help to minimize replication type issues when the machine account is newly created.

New Post: GetComputerNameByNetbootGuid returns Http 500 error..

cheredenine — Thu, 28 Feb 2013 09:32:32 GMT

Hello,

I'm using the deployment webservice with AD to obtain a computer name when imaging a computer. I've had this working fine through a browser and when doing some test imaging in a virtual machine; today, however, I just get a 500 internal server error!

If i access the webservice via a browser i can get the start page and from there look at the pages for the various option; the majority seem to work, but when i attempt to get a computer name by NetbootGUID or, conversely a NetbootGUID from the computer name i get this 500 error. I've looked at the webservice logs and they appear to be fine - I can see the process as the request is received and the data obtained with no hint of an error. The problem seems to occur at the last step of displaying the data in the browser.

Any hints?

Thanks!

New Post: Move Computer to Staging OU script question

tech3 — Thu, 21 Feb 2013 16:47:52 GMT

This is more a script question rather than the actual web service itself but I will throw it out there. So I am using the three scripts provided to move computers to a Staging OU and then to the OU I have assigned the computer at the end of my task sequence. So far it works perfect with one exception. I have the Z_MoveComputer_StagingOU.wsf script running as the first step in Preinstall. If computers are in AD it moves them perfect. If they are not in AD it errors out. No problem there as I just have it continue on error and it swaps the values of the OU. When the task sequence completes in final summary it pops up with the warning "move to staging ou was not successful rc=1". No worries I know that it worked. The question I have is there a way to modify the script so that the warning will not appear? Maybe a simple line that allows a return code 1? I am awful with scripting so I am not sure how to change it up. I have tried adding 1 to success codes on the task sequence step but that does not work.

New Post: Webservice on Server 2012

dsbloom — Thu, 21 Feb 2013 02:11:42 GMT

It was a clean install.

New Post: Webservice on Server 2012

h4x0r — Thu, 21 Feb 2013 02:05:06 GMT

Thanks for letting me know!

Was your Server 2012 install an upgrade from 2008 (R2), or was it a clean install?

New Post: Webservice on Server 2012

dsbloom — Thu, 21 Feb 2013 01:21:35 GMT

Yes, I have it installed on Server 2012 and it works fine.

New Post: DeploymentWebservice - Works Perfectly for AD, but not for MDT or SCCM!

jamesmealing — Tue, 19 Feb 2013 11:53:02 GMT

Hi All,

Figured it out now, I was being a plonker!

For some reason, I'd completely neglected to do the StoredProcedure part so obviously the MDT sections of the WebService was going to return a blank! I used the SQL script at the bottom of the following page to execute the stored procedures against the MDT database.

And then information from this page to troubleshoot the fact that I had the incorrect database selected in the DB field in the top right of the SQL query window;

The script executed succesfully with some warnings, related to fields which didn't exist. I'm guessing this is down to the fact that I'm using MDT 2012 Update 1, and the SQL Script was probably written for a earlier version with slightly different field names. But other than the missing fields it worked a treat :-)

The only issue is on the Documentation pages for the Deployment WebServices, the section about adding the StoredProcedures is appearing blank? Probably why I completely overlooked it in the first place...!

Perhaps Maik you could replace the info on this page if you get two mins?

Again, thank you so much for all the hard work you have done with the Deployment WebServices, WebFrontEnd etc, they're fab projects and make my life a whole world easier!

Kind Regards,

James

New Post: Source code for deployment webservice available?

cwb124 — Mon, 18 Feb 2013 22:54:19 GMT

Is the source code for this project available? Specifically I'd be interested in the VB code behind the MaikKoster.Deployment.SCCM.dll. I wrote an offline domain join web service and would like to consolidate the parts of the SCCM web service that we use and my offline domain join into one web service. I thought CodePlex was about open source stuff, but I can't find the code behind the deployment webservice, unless I'm not looking for it properly.

New Post: DeploymentWebservice - Works Perfectly for AD, but not for MDT or SCCM!

jamesmealing — Mon, 18 Feb 2013 17:30:33 GMT

Hi Maik/All,

Absolutely love the WebService and other MDT bits you have done, so thank you very much for those :-)

I am however having a slight issue with using the WebService from an MDT and SCCM point of view. I've installed the WebService (correctly to the best of my knowledge!) and the AD bit of it is working a treat... The MDT/SCCM bit however I am not having much luck with :-/
Through the web page, if I try to invoke one of the operations, such as GetRoles, it simply returns a blank page. I've looked through the logs and can see no errors/warning messages. I'm guessing it's something really dopey I'm doing (or not doing!) with permissions etc but for the life of me cannot work it out! Any pointers as to where I could start looking?

I have tried it with 'MDTDBIntegratedSecurity' set to 'True' which should work because the account to the best of my knowledge has permissions. I have also tried manually defining the 'MDTDBUser' and 'MDTDBPassword' fields using my personal domain credentials which I use everyday for my work with MDT and still no difference.

Any help would be hugely appreciated!!

Kind Regards,

James