Last post May 29, 2009 04:31 PM by tsch
May 26, 2009 03:42 PM|tsch|LINK
We are now moving to HMC 4.5 and desire to keep the transition seamless to the users. Therefore, they will use our ERP and affecting data, such as creating users or editing user attributes,
needs to reflect quickly and accurately in the hosted Exchange data. Since various applications from .NET to VBScript to EXEs can cause such changes recorded to a common SQL DB, there remains the idea that the existing SQL queue of changes to apply to Exchange
is a good way to get the data into Exchange. Therefore, I’d like to take the existing console applications – perhaps upgrading some or all to services – and have the create the relevant MPS requests and submit them the MPS Engine, residing on another domain’s
server on the same LAN. On the Microsoft Provisioning System Component Overview Technet page, this would be in the orange gradient box labeled “Custom Application”
Are there good examples of proper ways using native C# methods for manipulating XML to take the output of the Client Wrapper’s BuildBaseRequest() method and flesh it out for
a specific use of, say, either of the two aforementioned procedures? My thought is to start with
BuildBaseRequest() output and then add data for preferred DC, userPrincipalName, etc. Is this even the right approach?
Thank you for any help that you provide.
May 27, 2009 08:35 AM|tsch|LINK
Interestingly, the error message I get is "Process does not enough privleges to enumerate the security descriptor in order
to grant user access to the invoked method." with the mis-spelled "privleges". So, obviously it seems to me the current thread has not sufficient security. Is there a config file entry or registry entry or Client Wrapper method to indicate the correct credentials
or user account?
(Funny thing about the misspeling: Note the
technet entry for Hosted Active Directory::CreateUser. It incorrectly uses CreateBusinessUser for its own example. Or, is that correct on some level I don't understand? I don't have much confidence because the tree control frame on the left side of the
same page has misspellings of Hosted Active Directory ("Hosteded") and inconsistent applications of spaces. It's almost as bad as my own documentation and emails!)
May 27, 2009 03:43 PM|tsch|LINK
I am starting to think the MPS SDK has not changed materially since 2006 and
is the SDK for HMC integration and is not completely functional out side of a Dev Environment that is Win Server 2K3 with a VS install, preferably 2K5. See, for instance
Which is a blog post from an MS employee that helped create the SDK. Notice the end:
"If the MPS client is not installed and/or the machine is not a member of a valid (read: "working") MPS environment/domain, many of the integrated tools will not function properly... if you have troubles, make sure you can perform "normal" MPS operations
from the box outside of the VS environment."
This leads me to the following questions:
Visual Studio 2005
May 27, 2009 05:20 PM|mkostersitz|LINK
May 28, 2009 12:18 PM|tsch|LINK
I just wanted to be clear on one point. I am specifically asking what MPS-integration is possible developing apps on a XP Pro machine (not server OS), with VS 2005. You say,
"To make the SDK Tools/Visual Studio functional you need a connection to an MPS Configuration Database. Check out this blog post
http://blogs.msdn.com/mkostersitz/archive/2006/03/02/523757.aspx I wrote some time ago. It should get you started with a minimalist development environment. For that purpose you
can also virtualize the machines needed to save on Hardware."
At least in reading this post, it would suggest to me I need to do development on a Windows Server 2003 SP1 Machine, for instance, and I don't see anywhere about "a connection to an MPS Configuration Database" specifically. Am I missing something, or is
there another post?
We can build WS 2003 development machines, if necessary, but we don't want to. I want to stand up two developers and their hardward, but since they are integrating our ERP, I want them to have the same dev environment as the other 60-odd ERP developers,
which is XP/VS 2005/SQL 2Kx/etc.
Also, development is done on a different domain from the HMC domains. So, doing the development and having the integrating code run off the HMC domain but sendging requests to the HMC domain offers key flexibility we relied on when doing the segregated
address list integration a year and more ago.
Theoretically, I believe it should be possible with the right WS application with the rightly formatted XML request. I am continuing on exploring in that direction with this and other useful forum posts as my guide.
Am I missing anything on the big pciture of XP dev stations on one domain supporting an application posting XML to a different HMC domain. (Same LAN, same building)
May 28, 2009 03:23 PM|DmitriG|LINK
I just wanted to be clear on one point. I am specifically asking what MPS-integration is possible developing apps on a XP Pro machine (not server OS), with VS 2005.
Yes. It is possible. I used to do this back in 2006-2007. It is quite hard to setup because, in your case, you will need trust relationship between MPS client domain (on developer workstation) and MPS server domain. Account that you will use to execute MPS
requests must have rights similar to domain administrator in MPS domain and you can't just add this account to Domain Admins group since this account from trusted domain, so, you will have to do complex modifications in default AD ACLs to make this setup work.
Plus, you can't submit "trusted" request from outside of the MPS domain boundaries.
Another thing to think about. SDK is really required if you are going to develop MPS providers using C# or VB.Net. The rest of the SDK is convenient MPS procedures browser that you can use for reverse engineering, IntelliSense helper for XML editor (useless
BTW), and built-in support for provtest.exe and provnamespace.exe. If I understand you correct, you just what to generate some XML requests, send them to MPS and process response. For this sort of things you do need SDK. You can either utilize native MPS COM
Client (as it discussed at http://forums.asp.net/t/1287361.aspx) if you decide to have MPS client in different domain, or you can wrap MPS COM Client into web service, run this web service in MPS domain and
use ASP.NET authorization to control who can access this WS.
May 29, 2009 04:31 PM|tsch|LINK
Thank you all for your help. I am now using using the WS from one domain to send in my requests from another. I am succeeding, for instance, in creating OUs over there with code like this:
createOrganizationRequest.Data = orgdata;