11.3.1 remote manage group issues

Ever since we upgraded from 11.2.3a to 11.3.1 when I add people to my remote
manage group they are not given the rights to VL the devices folders and
users. I confirmed that all of the device folders and user source are still
configured under device management configuration. All previous upgrade users
are still functioning as normal. I had to add these rights manually to the
two new users I added post upgrade. Previous to the upgrade I could add
support people to this group that were limited to remote control and view to
all devices and all users (user source eDir) without me having to do
anything extra and the rights tab would populate on its own. Is this a bug
or by design change?

To be honest I was fumbling around with it and basically copied what was
already there from the pre upgrade users to the post upgrade users. I had
actually never explored the assigned rights tab before. So I think what your
saying is the populated rights entries that I saw that only had one VL
option checked in and the rest denied is a new feature populated by the
upgrade then I'm back to square one. Specifically I had to add under
"assigned rights" the device right to the context "/devices" and VL view
and all the rest of the options deny for this new user to see the
workstations. I never had to do that before. before I just added the user to
the remote mngt role and they were able to do only what they needed. Until I
manually added the assigned rights she saw nothing. Is this the way it is
now? the roles no longer give what is needed?
"Shaun Pond" wrote in message
news:[email protected]..
Ccps,
the VL rights are new with 11.3, designed to allow you to stop admins
seeing parts of the "tree" that they're not entitled to...
Shaun Pond
newly reminted as a Knowledge Professional

Similar Messages

Server 2012: Remote desktop licence manager not issuing licences

Hi,
I am battling with an problem which i cannot seem to resolve and no other forums actually come to a conclusion on how to resolve this problem!
I have a windows server 2012 server which is NOT part of a domain.
I have installed Remote Desktop Services and also installed the Remote Desktop License manager and i just cannot get the license manager to issue cals when users connect remotely via RDP
I have installed an extra two CAL's and tried using them as both a "Per User" and also "Per Device" but still does not work.
I have now run out of my grace period and cannot connect to the server at all
I have also tried changing some gpo's with no luck,
Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Licensing
"Use the specified RD license servers" = myservername
"Set the Remote Desktop licensing mode" = Per User
How can i fix this?
Thanks

Hi,
Thank you for posting in Windows Server Forum.
Have you seen that you have activated RDS License server before installing CAL?
Please check that the License Server should be part of ‘Terminal Server License’ group in Active Directory Domain Services. You can also configure RD License server manually by powershell commmand. Please check below article for information.
RD Licensing Configuration on Windows Server 2012
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx
In addition, please install below Hotfix and verify the result.
No RDS license when you connect to an RDS farm in Windows Server 2012
http://support.microsoft.com/kb/2916846
Hope it helps!
Thanks.
Dharmesh Solanki

Remote Management Multi-User security issue

Hello,
This issue concerns both Mountain Lion and Lion servers. If I'm not mistaken, the issue is also officially described by Apple in the Lion release about Remote Managemenr vs Screen Sharing features.
My question is simple and yet unanswered after hundreds of Internet searches:
Why on earth a non-Admin user has the right to Share and Control the screen of another (Admin) user being logged-in a (Mountain) Lion server? It looks like the trick is that "Remote Management" instead of "Screen Sharing" is active. So what? Why a non-Admin should be allowed at all to view another users desktop just by typing-in his/her own credentials?
Am I missing something or is Apple really out-of-security context? Our admin devoted significant effort to arrange access for the shared directories. For what? To find out that the Screen Sharing security under ARD Management (Remote Management) is non-existent?
Am I terribly wrong?
Any feedback will be highly appreciated.
D.

http://www.apple.com/feedback/

RV042 issue remote management access

Installed on two RV042 links with adsl load balance, everything works fine, except that an error occurs during a time I can access the remote management via Web RV042 both the LAN and the WAN, only after a while when accessing the page appears to login, but when you enter your username and password the browser is trying to give an error, the connection to the internet works normal again and I can only access the remote management to disconnect and reconnect the RV042, but updated the firmware the error continues, my RV042 is:
RV042 V03
Firmware v4.1.1.01-sp
I changed the default https port (443), to other ports but the error continues, someone had this problem?
André Szytko

hi there,
i can use google translate to try understanding your post. but i think its better for you to explain in english mate
regards,

Odd firewall issue, remote management works on 1 server, not the other

I've enabled port forwarding, made sure I mapped address to mac ports in the DHCP client settings (to ensure a "static" address), and choose the correct IP address for port forwarding. Then, I enable remote management on my snow leopard laptop then connect remotely (from outside lan) and it works. To the reverse, my 10.5.8 OS X server set up with the same items (although the menus are slightly different given each are diff versions), change port forwarding IP addresses on router, and try outside the lan from the client to connect to the server. Failed. Of course, remote management works fine on the LAN in both directions, only fails from snow leopard client to 10.5.8 server when not on same lan.
So, to illustrate:
10.5.8 (client) ---> internet --> router --> snow leopard laptop (server) WORKS!!
snow leopard laptop (client) --> internet --> router --> 10.5.8 (server) FAILS!!!
client --> LAN --> server (in either direction) WORKS!!
Message was edited by: julebuggy

I've enabled port forwarding, made sure I mapped address to mac ports in the DHCP client settings (to ensure a "static" address), and choose the correct IP address for port forwarding. Then, I enable remote management on my snow leopard laptop then connect remotely (from outside lan) and it works. To the reverse, my 10.5.8 OS X server set up with the same items (although the menus are slightly different given each are diff versions), change port forwarding IP addresses on router, and try outside the lan from the client to connect to the server. Failed. Of course, remote management works fine on the LAN in both directions, only fails from snow leopard client to 10.5.8 server when not on same lan.
So, to illustrate:
10.5.8 (client) ---> internet --> router --> snow leopard laptop (server) WORKS!!
snow leopard laptop (client) --> internet --> router --> 10.5.8 (server) FAILS!!!
client --> LAN --> server (in either direction) WORKS!!
Message was edited by: julebuggy

Can't find "Windows Remote Management (WinRM)" in Group Policy Management console

So looking at different scenarios for enabling WinRM / PSRemote. Find all kinds of information on how to do it... stoked right!? Not so much, I can't find Windows Remote Management (WinRM) where it should be, or anywhere else. WTF? Any ideas here kids?And
OBTW, Domain Functional Level is 2008 R2 with Windows 2012 R2 DC's.

Oh man, found the answer... Doh!
Run from an elevated command prompt;
robocopy "%windir%\policydefinitions" "\\%userdnsdomain%\sysvol\%userdnsdomain%\policies\policydefinitions" /s
So there you go.

Mountain Lion Server: add network user to remote management

Hi,
So recently I have upgraded from Lion Server to ML Server. A little disappointing, but whatever, I've moved on and got everything almost back to where I had it with Lion.
My last few issues I believe are related but can't quite figure it out. In Lion I have an admin profile and then a network user profile that I used on my MBP bound with AD. I'm at the stage where my nre network user can log in on the server machine but I can't log in as the network user via screen sharing. I can't add a network user to Remote Management, and with Remote Management enabled Screen Sharing is greyed out. I'd really like this to work.
My second problem is that I can't bind my MBP to the server but even when bound the network user account can't log in.
Any body have any ideas?
Thanks!

I had this problem on a clean install.
The solution was incredibly simple for me, but only after I saw Ross.M's note about opening the Users & Groups settings panel (in the OS System Prefs, not in server) and rebinding to OD server under Login Options.
That was not the solution for me, but under Login Options I discovered a previously unnoticed pref for "Allow network users to login at login window." I had this option set (apparently by default) to "Only these network users:" but with an empty list. Adding my users to the list made it work perfectly.
Talk about KISS

Remote Management service does not start

Has Novell got a fix for the issue where the Remote Management services
fails to start automatically on XP workstations? As we upgrade our clients
to XP, this has become a major headache. The service can be started
manually, and then the Remote Control feature of ZFD will work, providing
the firewall is disabled.

Workaround is to create a batch file and put in the command:
net start "remote management"
Create a shortcut to this batch file and put it in the startup group of
All Users in the "document and settings".
Phong Nguyen
> Novell Client 4.91 will not include any of ZFD 3.x services so you'll
need
> to upgrade to 4 or preferrably ZDM 6.5. This weekend I kicked off a
ZFD 3.2
> SP3 to 6.5 SP1 migration. Even without the extra services its worth it
just
> from a support stand point.
>
> Do the details posted in this thread help any?...
>
> Newsgroups: novell.support.zenworks.desktops.3x.remote-control
> Subject: ZfD3.2, NetWare 6.0, XPsp2, will it work?
> Message-ID: <azXhd.717$[email protected]>
> Date: Wed, 03 Nov 2004 02:41:10 GMT
>
> 1. Set Windows Firewall/ICS service to manual
> 2. Set Windows Firewall/ICS service to start before Remote Management
(ie.
> Remote Management service depends on Firewall/ICS and Workstation
Manager
> services)
> 3. Configure Windows Firewall exceptions for wuser32.exe, open ports
1761 -
> 1763 (you need others depends on the services you use, see TID below)
>
> What Ports are used by ZENworks Remote Management Agent?
> http://support.novell.com/cgi-bin/se...?/10054960.htm
>
> Support for Windows XP SP2 on ZENworks for Desktops
> http://support.novell.com/cgi-bin/se...?/10092958.htm
>
> --
> Tony Pedretti
>
>

Guide to remote manage Hyper-V servers and VM's in workgroups or standalone

This guide is based on the following 3 products:
Windows server 2012 (core)
Windows 8
Hyper-V server v3 / Hyper-V server 2012
The following guide will enable you to:
1: remotely manage your Hyper-V Virtual Machines with Hyper-V manager
2: remotely manage your Hyper-V servers' firewall with a MMC snap-in.
3: remotely manage your Hyper-V server (2012) with server manager
! This should also work for Core installations of server 2012, but I haven't tried.
This guide is purely focussed on servers in a WORKGROUP, or as a stand alone.
I CAN NOT tell you what you need to do to get it working in a domain.
* You can run these commands straight from the console (Physically at the machine) or through RDP.
* You will need to be logged on as an administrator.
* Commands are listed in somewhat random order; I do however advise to follow the steps as listed.
* Commands with ? in front of them are only ment to be helpfull for troubleshooting,
* and to identify settings and changes made.
* Commands and instructions with ! in front of them are mandatory.
- server: means the server core or hyper-v server (non gui)
- client: means the machine you want to use for remote administration.
- Some commands are spread over 2 lines; be sure to copy the full syntax.
> To enable the Hyper-V manager to connect to your server, you need to perform the following 2 actions: (Assuming you have already installed the feature)
1:
! Client: Locate the C:\Windows\System32\Drivers\etc\hosts file.
! right-click --> properties --> security
! click --> edit --> add --> YOURUSERNAME or Administrator --> OK
! then select this new user, and tick the "modify"-box under the "allow"-section.
! apply the change, and close.
! doubleclick the file, and open with notepad
! add the ip-address and name of your server (no // or other crap needed)
! Save the file
# I recommend putting a shortcut to this file on the desktop.
# If you change the ip-address of your server (e.g. move the server from staging to a live environment)
# you might forget to do so in the hosts file.
# Hyper-V manager, MMC, RSAT, and Server-manager all rely on the hosts-file to resolve the name.
# some of these might connect to their respective service on an i.p.-level, but some don't.
# This is the main reason you need to modify this file.
! USE AN ELEVATED CMD/POWERSHELL PROMPT TO CONTINUE !
# the next config needs to be done on windows 8.
# It seems that it's already preconfigured under server 2012
2:
! Client: dcomcnfg
! open component services --> computers
! right-click -> my computer -> properties
! select "COM SECURITY" tab
! under "ACCESS PERMISSIONS" select "edit limits"
! select "ANONYMOUS LOGON", and tick "remote access" under ALLOW
# Without this adjustment, you can't connect to your Hyper-V server
# with the Hyper-V manager if you're not in a domain.
> And if you haven't done so already... make sure you have enabled remote management number 4 on the Hyper-V server console.
> Next, is to get the MMC firewall snap-in working.
The reason for this, is to have a GUI available to configure it.
If you're happy without it, you may skip this and use a shell instead to do so.
? server: netsh advfirewall show currentprofile
# shows the current profile (public/domain/private) and its settings
# depending on your needs, you should set the right profile to fit your needs.
# You can easily do this when the MMC snap-in is done. (after you've followed these steps)
! server: netsh advfirewall set currentprofile settings remotemanagement enable
# enables remote management of the firewall on an application level
# (In other words: allows the firewall to be remotely managed)
! server: netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yes
# allows remote management of the firewall, through the required firewall ports with TCP protocol.
# 4 rules will be updated to allow access: public & Domain, dynamic and endpoint-mapper.
# You can disable/add/change the rule from the MMC snap-in after finishing this guide.
# e.g. set the firewall through the MMC-GUI to only allow specific ip-addresses etc.
? server: netsh advfirewall firewall show rule all
# Shows a list of available rules, and their current state.
# when run from cmd, the list exceeds the maximum length for review.
# (from cmd,type:) start powershell, and run the command from there.
! Client: cmdkey /add:YOURSERVERNAME /user:USERNAMEONTHESERVER /pass:THEPASSWORDOFTHATUSER
# I recommend you to use a username with enough privileges for management
# All capital letters need to be replaced with your input
# CMD answers "credential added successfully" when you're done
! Client: locate MMC, and run it as an admin.
# In windows 8/2012, go to search and type MMC. Right-click the icon,
# and choose run as admin on the bar below.
! Client: application MMC: select "file" --> Add/remove snap-in
! --> (left pane) scroll down to "windows firewall" --> select and click "add"
! select "another computer"
! type the name of the server you want to manage (NO workgroup/ or //, just same name as you typed for cmdkey)
* Part 2 is done.
# Have a look by doubleclicking the firewall icon in the left pane.
# It looks and works the same as the GUI version that you are familiar with.
! Next is the Server Manager.
# Follow the steps listed to get your server listed and manageable in the server manager.
! Client: Open the created Firewall snap-in for your server.
! Find the 3 "Remote Event Log Management" entries in the list of INBOUND rules, and enable them.
! Open powershell --> in cmd windows, type: start powershell
! run the following line in powershell
! Client: in C:\Windows\system32> set-item WSMAN:\localhost\client\trustedhosts -value YOURSERVERNAME -concatenate
# WinRM Security Configuration.
# This command modifies the TrustedHosts list for the WinRM client. The computers in the TrustedHosts list might not be
# authenticated. The client might send credential information to these computers. Are you sure that you want to modify
# this list?
# [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): y
# I recommend to choose yes; unless you like to pull some more hairs...
! server: winrm qc
# WinRM service is already running on this machine.
# WinRM is not set up to allow remote access to this machine for management.
# The following changes must be made:
# Configure LocalAccountTokenFilterPolicy to grant administrative rights remotely
# to local users.
# Make the changes? y / n
! select yes
! Client: open the server 2012 server manager
! click manage -> add server
! select the DNS tab, and type the name of your server
Done.
You can now manage your remote server through the familiar computer management GUI.
! Right-click your remote server, and select "Computer Management"
A few side notes:
? The Performance tab seems to list the local machine's performance, in stead of the remote servers'
? If you want Windows server backup, you need to right-click the server in the server manager, and select "add roles and features.
? it will then become available under the "computer management" of the remote server.
If you liked this guide you may thank my employer, Mr. Chris W.
for giving me the time to work it all out.
Cheers!

As a little update to the post, I'd like to add that replication, clustering and migration will not work in workgroup environments. Unless someone can provide an additional guide for this, I'd recommend anyone to no even bother to try.
To manage the standalone hyper-v server in a remote location over the internet, I would recommend the following:
Install windows 8 pro (x86 uses less resources!) as a vm on the host, and assign 2 network connections to it.
1 external (shared with host) (be sure you have a dedicated ip-address for it!)
1 internal connection.
What I did was this:
As soon as you've installed the win8 guest, proceed with the guide as described.
For the 1st step of the guide (hosts-file) use the ip-address you will later assign to the "internal" network switch of the host!
In my example, I'm using 10.0.0.1 for the host, and 10.0.0.2 for the guest.
To be clear: I first used the guide on a LAN-environment, and did all the steps from a "real" client to server on the LAN.
Then, installed the win8 guest on the host using the "real" clients' hyper-v manager over the LAN.
Next, assigned the 2 network connections to the VM, and configured them as follows:
external - as you would to be able to make your guest reach the internet.
internal - I used the following config:
ip-address: 10.0.0.2
subnet: 255.255.255.252
gateway - blank
dns - Blank
Now, when you get to the console of the hyper-v server (host) or RDP to it, go to network settings.
You'll see that the internal card has been added here as well.
Configure it as follows:
ip-address: static - 10.0.0.1
subnet: 255.255.255.252
gateway - blank
dns - blank
You should now be able to ping your guest (win8) on 10.0.0.2 if it's running.
Don't forget to enable ping response (option 4 on the host) to test connectivity the other way around as well (guest to host)
When you're done, you'll be able to RDP to the guest OS over the internet, and then connect to the host with server manager, hyper-v manager, and MMC.
Don't forget to enable each module on the hosts' firewall to make the snap-ins work!
Remote volume management requires your guest/client firewall INcoming ports to be enabled as well! not just the host.
Either update the firewall rules from the MMC gui as described in the guide, or use the following commands on the
hosts' powershell:
Enable the firewall rules with the command Enable-NetFirewallRule -DisplayGroup "USE_THE_COMMANDS_BELOW" (include the " " in the command)
Remote Service Management
Remote Volume Management
Remote Event Log Management
Remote Scheduled Tasks Management
Windows Firewall Remote Management
Windows Remote Management
You can get the list with Get-NetFirewallRule -DisplayName *management*
You can get the list with Get-NetFirewallRule -DisplayName *remote*
Commands provided with credits to F. verstegen
Cheers,
Michael.
Sigh...

How to execute vb script with out using Remote manager in oim 11g r2

Hi Currently,
i have a requirement to execute vb script (present on a remote machine in which connector server is installed) from oim machine while using Exchange connector (11.1.1.6).
This can be achieved by using remote manager,but i dont want to use remote manager.
Hence decided to use Action scripts.
As per connector configuration,
i have configured Action scripts in Lookup.Exchange.UM.Configuration lookup definition, by means of three entries
After Create Action Language      Shell
After Create Action Target           Resource
After Create Action File              /home/scripts/Disable.bat
Disable.bat has the following ,
Powershell.exe -File C:\scripts\Setup.vbs
-%Log on Name%
Exit
As Setup.vbs is expecting a parameter of log on name, i was providing the same.
But while creating the user,as this script gets called, getting the following error and hence 'create User' is getting failed.
Problem while PowerShell execution System.Management.Automation.RemoteException: This task does not support recipients of this type. The specified recipient XXXXXXXXXXX...XXXXX is of type UserMailbox. Please make sure that this recipient matches the required recipient type for this task.
While provisioning the user to Exchange , i have selected 'Recepient type' as 'User Mail box' explicitly, but still getting the error.
Please provide any pointers to resolve the issue.
Thanks in advance
Kumar

As far as I know Oracle and MySQL are two different products.
Why do you clutter an Oracle forum with MySQL questions?
If MySQL is such a tremendous RDBMS, like many people state (as 'free' means per definition better),
why don't you visit a MySQL forum where fellow MySQL aficionados can answer you MySQL questions?
In short, why don't you stop abusing Oracle forums?
Sybrand Bakker
Senior Oracle DBA

Install Failing when attempted to Add a new Management Server into SCSM Management Group

Hello Experts
I am adding a additional MS into my current SCSM 2012 sp1 MANAGEMENT Group. But its failing with the below error message .One thing is little wiered here is ...that the wizard fails with the message that the UPGARDE FAILED , but I am not rying to upgrade
, I am adding a MS on a new 2012 vm. It goes all the way and install the services with the account , but then it rollbacks everything I am installing the bits with the same account which is the admin on the workflow server . I have created a registry
key ServicesPipeTimeout to 600000ms , but still no luck . The new VM is all up to date with patches , the sdk/config account is the admin on the new ms vm . The service manager db is a cluster , not sure if that's wats causing it .
SCSM2012 SP1
Primary Workflow MS : WIN2008R2
SQL CLUSTER : 2008R2SP1
New MS :- WIN2012
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (B8:98) [16:36:03:050]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (B8:78) [16:36:05:044]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156350899,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (B8:78) [16:36:05:044]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (B8:78) [16:36:05:046]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)

D5DB645B01E7},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Core,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:669]: Executing op: AssemblyPublish(Feature=SMCommon,Component={4D0CB3BB-D941-408A-AA30-F8B7996AB220},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.Packaging,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:675]: Executing op: AssemblyPublish(Feature=SMCommon,Component={B6133F85-0B89-4120-ADFD-9A426FB7D5A3},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager.Common,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:681]: Executing op: AssemblyPublish(Feature=SMCommon,Component={58A6B313-BD98-46E0-B344-0D6861535208},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.ServiceManager,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:688]: Executing op: AssemblyPublish(Feature=SMCommon,Component={41071460-6573-41C8-AED8-06CEC0D0AFB9},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.DataWarehouse,fileVersion="7.5.2905.0",version="7.0.5000.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:693]: Executing op: AssemblyPublish(Feature=SMCommon,Component={E51AEF3C-9B2D-4B0E-AB7E-AD0423899C39},AssemblyType=1,,AssemblyName=Microsoft.EnterpriseManagement.OperationsManager,fileVersion="6.0.6278.0",version="6.0.4900.0",culture="neutral",publicKeyToken="31BF3856AD364E35",processorArchitecture="MSIL",)
MSI (s) (80:88) [11:29:02:713]: Executing op: AssemblyPublish(Feature=SMCommon,Component={9718BF1D-6A9F-3406-A992-630F7EF2F164},AssemblyType=2,,AssemblyName=Microsoft.VC90.CRT,version="9.0.30729.1",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32",)
MSI (s) (80:88) [11:29:02:720]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:721]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:722]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,,)
MSI (s) (80:88) [11:29:02:724]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall.62894CB9_4320_40DB_B4E4_C0347FAB97B6,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:725]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitUninstall,,)
MSI (s) (80:88) [11:29:02:726]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitUninstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,)
MSI (s) (80:88) [11:29:02:726]: Executing op: ActionStart(Name=NetFxExecuteNativeImageCommitInstall,,)
MSI (s) (80:88) [11:29:02:728]: Executing op: CustomActionSchedule(Action=NetFxExecuteNativeImageCommitInstall,ActionType=3649,Source=BinaryData,Target=ExecNetFx,CustomActionData=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft
System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll"
/queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe
install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1?500?C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service
Manager\Microsoft.EnterpriseM
MSI (s) (80:88) [11:29:02:729]: Executing op: ActionStart(Name=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,Description=Configure Config Service,)
MSI (s) (80:88) [11:29:02:734]: Executing op: CustomActionSchedule(Action=_ConfigureConfigService.D2179E31_E456_401A_A820_CEBB135E3429,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMCFG)
MSI (s) (80:88) [11:29:02:736]: Executing op: ActionStart(Name=_ConfigureSDKConfigService,,)
MSI (s) (80:88) [11:29:02:737]: Executing op: CustomActionSchedule(Action=_ConfigureSDKConfigService,ActionType=3585,Source=BinaryData,Target=ConfigureSDKConfigService,CustomActionData=1 OMSDK)
MSI (s) (80:88) [11:29:02:738]: Executing op: ActionStart(Name=_WaitForSDKServiceStart,,)
MSI (s) (80:88) [11:29:02:840]: Executing op: CustomActionSchedule(Action=_WaitForSDKServiceStart,ActionType=1537,Source=BinaryData,Target=WaitForSDKServiceStart,)
MSI (s) (80:88) [11:29:02:924]: Executing op: ActionStart(Name=_RegisterSdkSCP,,)
MSI (s) (80:88) [11:29:02:944]: Executing op: CustomActionSchedule(Action=_RegisterSdkSCP,ActionType=1089,Source=BinaryData,Target=RegisterSdkSCP,CustomActionData=SCSMPROD|DOMAIN\_SVCACCT|SMSDKSCP)
MSI (s) (80:6C) [11:29:03:103]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI16CE.tmp, Entrypoint: RegisterSdkSCP
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI16CE.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP
RegisterSdkSCP: There is no previous serviceConnectionPoint
RegisterSdkSCP: Creating New serviceConnectionPoint
RegisterSdkSCP: Adding ACL for current user: DOMAIN\_SVCACCT
RegisterSdkSCP: Adding ACL for SM Admini: DOMAIN\_SVCACCT
RegisterSdkSCP: Error: Access is denied.
StackTrace:    at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.SetInfo()
   at System.DirectoryServices.DirectoryEntry.CommitChanges()
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.RegisterSdkSCP(Session session)
MSI (s) (80:6C) [11:29:10:243]: NOTE: custom action _RegisterSdkSCP unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:10:246]: Executing op: ActionStart(Name=_SetupSdkDefaultConnector,Description=Setting SDK default connector,)
CustomAction _RegisterSdkSCP returned actual error code 1603 but will be translated to success due to continue marking
MSI (s) (80:88) [11:29:10:265]: Executing op: CustomActionSchedule(Action=_SetupSdkDefaultConnector,ActionType=17921,Source=BinaryData,Target=SetupSdkDefaultConnector,CustomActionData=EDVXSCSMWEBPP02)
MSI (s) (80:88) [11:29:10:366]: Executing op: ActionStart(Name=_CreateSetupUser,,)
MSI (s) (80:88) [11:29:10:381]: Executing op: CustomActionSchedule(Action=_CreateSetupUser,ActionType=1537,Source=BinaryData,Target=CreateSetupUser,CustomActionData=DOMAIN\_SVCACCT)
MSI (s) (80:88) [11:29:10:461]: Executing op: ActionStart(Name=_CreateInstanceQualityRelationship,Description=Creating Default Instances, Qualities And There Relationships,)
MSI (s) (80:88) [11:29:10:481]: Executing op: CustomActionSchedule(Action=_CreateInstanceQualityRelationship,ActionType=17921,Source=BinaryData,Target=CreateInstanceQualityRelationship,CustomActionData=Cmdb^Microsoft.SystemCenter.ResourceAccessLayer.CmdbResourceStore^Ral.CmdbResourceStore.Cmdb^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Ods^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Ods^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Workflows^Microsoft.SystemCenter.ResourceAccessLayer.SqlResourceStore^Ral.SqlResourceStore.Workflows^SCSMSMDBDOMAIN,DOMAIN^ServiceManager^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Orchestration^Microsoft.SystemCenter.ResourceAccessLayer.DagResourceStore^Ral.DagResourceStore.Orchestration^EDVXSCSMWEBPP02^Dag^Microsoft.SystemCenter.ResourceAccessLayer.Stores|Sdk^Microsoft.SystemCenter.ResourceAccessLayer.SdkResourceStore^Ral.SdkResourceStore.Sdk^EDVXSCSMWEBPP02^Sdk^Microsoft.SystemCenter.ResourceAccessLayer.Stores$Cmdb^Cmdb|Ods^Ods|Workflows^Wo
MSI (s) (80:88) [11:29:10:551]: Executing op: ActionStart(Name=_CreateSLAOOBMetric,,)
MSI (s) (80:88) [11:29:10:593]: Executing op: CustomActionSchedule(Action=_CreateSLAOOBMetric,ActionType=1537,Source=BinaryData,Target=CreateSLAOOBMetric,)
MSI (s) (80:88) [11:29:10:669]: Executing op: ActionStart(Name=_AddAuthenticatedUserToSmEndusersRole,,)
MSI (s) (80:88) [11:29:10:687]: Executing op: CustomActionSchedule(Action=_AddAuthenticatedUserToSmEndusersRole,ActionType=17921,Source=BinaryData,Target=AddUserGroupToSmRole,CustomActionData=SERVERNAMEDOMAIN,DOMAIN|0CDDEB2B-5AC7-4E9b-8918-F73A5A5DC5FA|S-1-5-11)
MSI (s) (80:88) [11:29:10:764]: Executing op: ActionStart(Name=PublishFeatures,Description=Publishing product features,Template=[1])
MSI (s) (80:88) [11:29:10:769]: Executing op: FeaturePublish(Feature=SMCommon,,Absent=2,Component=(q3HBAv]i@qJ'%Q!&u`-E'vFHJKp&?B*BP3I&v8CI)GV$dS}K9o{`+oQzOH`6rk8o}k)$9h9ht?25ep*M5[kQmAiu8ksDfcfd?7Y`cA}%6azL=&%e(j@mj@Fz,ecq(qrp8](TKe3L$PCRH97spltW=ku%.hsb*,Om8nB9k-6cA0[3pMQTZ)ilXhqI.}^o8,EuQO7^U_3+@[M`@}[t9u8Wo6!tFc%bh)^7q6wW=apEHCHH1,?v,UEvGBSJArZu~HLod%Kb5o96e+p$903LI])2$p$F%OJdG^%+A=LH+73@4VPU6Grpj92,@+LF6KK25&]=f`,Pw3-%=3zM^iId4@ZCcxSHi&g39aNS8{R&72hWL`[email protected]`]AQmIfehM.h8y$eKidM0ZZCIg^udzEY?vKfT%PHraR*_a5.zP5_@[KW{oCEn$OB[,Y5D*`m9ByA])z,POCbb@sj&oXSAAcoGYM11_t!LQ[A2'u.90@8@Eats}$VHsbIFnRS=HM!!AA67_?kk^q?LXxN=r$8P(zZWMJJ{9@Z'[&R=ibW(AelUb.T7J9-G*B~='`,6hc~mWukk*QjX6`=?+MOCxGuQnGmy*71a$.d=q2UJvQ$^-E1ev?yK?40?AC856b78PAvp@-+AM.W?c~waDTv0,B3zl1iw%vO9)BKj!jy7~r^wE3]d*T-@NwxfGl[ns7%KANUrxZ_9)ODbn-q(ifd)oMIA18&?By'*2%,lY+,!UmZHa]_8+TSP[td}bT-CL%NNDP3?Z*yqPzZpJL.g@_oYZZZ@f!r?*1+']Zj]ZqjdIrE93ZaoSS_`udf%hNKO=9j?aFhCl*?,uleMNZ1Z~ZE9FqKxu+Isz3ow_9L8eB^=3X9%1XjT_huv(S=Kofh9JKrEq.?bB!L`vCwRLC3@2y4WO-0'Ic%eNDY,x-y@1n30[^'z+cLCX]e[=7a8'W6k*?}q&'br-YB(.!`@fw0~&p`8-=Mnx6qys!X9TQW^09zZ@pU
MSI (s) (80:88) [11:29:10:821]: Executing op: FeaturePublish(Feature=SMServer,,Absent=2,Component=Ik{Op{5Kr=GT6Le$}XC3c6,M6L((V9pkVNH,10cG1+tmy*`TG?4+OQ_V,p$dVCsu8xeQf9Brt8)ud$Sf^SsJTSpso8TFvFZg+*V!vIFSk4eIY98NOU2f+BvOK_yzaR8Je9TA*L3kFh1Q^c{'C@}z5=0HxnJ+Ye5m?Bt&'[email protected][Q%j-V=`9aWmoOnwf@bG~tm6{U72@o$9HI1rY8sqD'n71MVZ?sjtIJ^RR~x(I9V?3bEV9=E%_oQj-dfO26gb,)~X?v_5H&}8OBC,Zd3FO*6x?^&vV^oAnT8W]VCJ5{1D?cF2hz^y{{p&uDdwpd}h8`NZJv_a3H!)feXUfw]v?_@*Otsy%B'YK$aq~=M9AbjW10uEDJQXE)3'L82.?,2W6FLDxVGn^9T&=1y~9]TMt7^XvHXTYuO[z=6}@L_^wh,(g}ZqJ^O1bEhS?r)iI.5E.A7i&@zDQdtV='FS(W8wl!b1yF'DVKLY={M5MYbn*wOxsSgjVY3D@oGP5W(_$7[fx&!R(pHF=T%$LsMp7?spYDG3w!zC?5B2{8,F)[H!uUfS0'_m?$WG=P,jT7WOo2W_*dsE@=5jq^lyW?1(8?&32w,NAkc8wJs8GCEu1_2Xc^g[?VhL-,XO~{,H,a]zRr,2=]XThvu.EBR0v?pCd&1@?-Rud!Nf*yt-S'NdXk~P99PFN(w0J9RAmQC40IY9AQKBcb!S?=CnT=EuzE1q=w)`V(40a'jdyXR+pN}`A.UP3IQjE(9xOtNZV!)e9YJ=NzOE[$(Itp!&{M^09-FPfKKbD1uIz}V_z3K^9t3U4Tvo(Gq8eyV`z3K^9b)@zEvo(Gq}1+M!-vLb9Y{kU8s)9cs`p`b,X*][=!CtK^UfdUy]u[kDa&5C?dr&Nb_m6L%E'Tes__*W=Cf)0-^yp**S{$*8j'~D=bv,m!@w5F5^Yvr?u^T??[Dr^?X5&DC{BJ]9S.IY?X_+EYCq`~aII17]HE$Y=G,N.-Z]Nu9F
MSI (s) (80:88) [11:29:10:862]: Executing op: FeaturePublish(Feature=SMConsole,,Absent=2,Component=-t's,QtH^Aw+6FO*=Se(iQRgqk%_g=dT63!k9!rD@dhrK&d7h=K@C5tXh+0WxiGiG5${}83t&igNy{fY&JO-tv~W3Ah1fGYB1.`B!^o%uu!H)9R}66fvSA0Wv%z,9-1jG9y?v}nwk!s?K=B`'Nk^.93`591RA^Ebzru^Hg?vMA6WScC*[V.DUtMfGl+Os98*Wc&+YY[2abg{3@n-]@5Gxvon=g76CVQ~Ijn^X9P2H12*)v(!KYwG+v*QS={[,{TMbA'(jZhl`KmU$?Vez&@)YK[mVm~2X&18E@])Ry4^X^KQ`vnk@+v{B?dAn}YD*9*5S_~w'M?2c?s8Sf^yA)9@nE@ABBSrt8T++.V{d4gb6,p$83`m4?OV9^r0F`IO[`o_-lb2}91AcKjfKCE2=q?*Gk,g'?2O7pkHrC*](^yu[K}-S9elzyj=2zt[iF(M2nb-z9sgF?29J6($ZQAS%izDO9oq$k`dG4]?OicWT^[Y=AlFJBP05%gId7HBQ9jDv?bh(2W~-B+J%ZHxQK2k4?Umi{dWK[GK_mG&(el!^AR,YT-X9P-m(9%C-l..z==Oh(RE,xmDS6=!lKz,O=&,deE`++iQ5VCXL[Y^Z?LB7r)u}k4n7=LtnTJwZA)eY8vfB@7vvdYD(a8ZU=qVm47sBI?iaZk6p!S]8?6D_x4Z7cJjqfl~xo!zh@7X%ORA?XADrzW?JWEfO9?9@$3t_Qr`{kPS!rsu19(OfCf'~0~Po4[nv@Xp]=P^LkdkaG14a99ww^FX2@Amv.^j+f3M*e)H?o6qr@fx9b'rGbrKH@FR8}kA.9^kv{98D@Qy?cq4uLo2o=_8G4&1&IqY(CeD&$F@G@MdV7cI5ewzftyD$`o_k=~X5yoL3!&A`NSB.WH!LA3(1Rmkk9?ethX(x,HWR9_OUZ=H!k3Xko]}oWUVJ@QG{ztU'eAplc=@70chp9&@F34p~'T)CfM[I(VWm9.a`6U-hvjpUZDg96]v?@_S7.CdN=Uj
MSI (s) (80:88) [11:29:10:908]: Executing op: ActionStart(Name=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,,)
MSI (s) (80:88) [11:29:10:910]: Executing op: CustomActionSchedule(Action=_StartNamedServices_CoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9,ActionType=3649,Source=BinaryData,Target=StartNamedServices,CustomActionData=HealthService System Center Management
APM)
MSI (s) (80:88) [11:29:10:913]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:29:10:918]: Executing op: CleanupConfigData()
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:918]: Executing op: RegisterPatchOrder(Continue=0,SequenceType=1,Remove=0)
MSI (s) (80:88) [11:29:10:918]: Note: 1: 1402 2: UNKNOWN\Products\5BA67A970AE3F4C4989BC10A4083CEE2\Patches 3: 2
MSI (s) (80:88) [11:29:10:923]: Executing op: ProductPublish(PackageKey={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7})
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:932]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2 3: 2
MSI (s) (80:88) [11:29:10:942]: Executing op: UpgradeCodePublish(UpgradeCode={4F70C213-6F45-4AA0-8994-1A09CBF27D77})
MSI (s) (80:88) [11:29:10:947]: Executing op: SourceListPublish(,,DiskPromptTemplate=Please Insert Disk 1,,NumberOfDisks=1)
MSI (s) (80:88) [11:29:10:947]: Note: 1: 1402 2: UNKNOWN\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList 3: 2
MSI (s) (80:88) [11:29:10:948]: Executing op: ProductPublishClient(,,)
MSI (s) (80:88) [11:29:10:949]: Executing op: SourceListRegisterLastUsed(SourceProduct={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},LastUsedSource=E:\SCSM2012sp1\amd64\Setup\Server\)
MSI (s) (80:88) [11:29:10:949]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (80:88) [11:29:10:963]: Specifed source is already in a list.
MSI (s) (80:88) [11:29:10:963]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (80:88) [11:29:10:963]: Adding new sources is allowed.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedSource to: E:\SCSM2012sp1\amd64\Setup\Server\.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedType to: n.
MSI (s) (80:88) [11:29:10:963]: Set LastUsedIndex to: 1.
MSI (s) (80:88) [11:29:10:964]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:29:10:979]: Executing op: CustomActionSchedule(Action=_EnabledDiscoveryDataAuthorization,ActionType=1537,Source=BinaryData,Target=EnabledDiscoveryDataAuthorization,)
MSI (s) (80:88) [11:29:11:086]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:29:11:104]: Executing op: CustomActionSchedule(Action=_RegisterVssExpressWriterSM,ActionType=1089,Source=BinaryData,Target=RegisterVssExpressWriterSM,CustomActionData=SCSMSMDBDOMAIN,DOMAIN|ServiceManager)
MSI (s) (80:EC) [11:29:11:173]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI36AB.tmp, Entrypoint: RegisterVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI36AB.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RegisterVssExpressWriterSM
RegisterVssExpressWriter: Registering VSS express writer.
MSI (s) (80:EC) [11:29:15:881]: NOTE: custom action _RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
MSI (s) (80:88) [11:29:15:884]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
RegisterVssExpressWriter: Registered VSS express writer.
MSI (s) (80:88) [11:29:15:896]: Executing op: CustomActionSchedule(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:88) [11:29:15:975]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=639325328)
MSI (s) (80:88) [11:29:42:385]: An error occured while refreshing environment variables updated during the installation of ''. Some users logged on to the machine may not see these changes until they log off and then log back on.
MSI (s) (80:88) [11:29:42:445]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:88) [11:29:42:446]: User policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:446]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:88) [11:29:42:452]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (80:54) [11:29:42:890]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB293.tmp, Entrypoint: StopNamedServices
MSI (s) (80:BC) [11:29:43:709]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIB40B.tmp, Entrypoint: ExecNetFx
MSI (s) (80:BC) [11:29:43:731]: Generating random cookie.
MSI (s) (80:BC) [11:29:44:395]: Created Custom Action Server with PID 4800 (0x12C0).
MSI (s) (80:F0) [11:29:45:368]: Running as a service.
MSI (s) (80:F8) [11:29:45:393]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (80:F0) [11:29:45:460]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCA7.tmp, Entrypoint: ExecNetFx
MSI (s) (80:F4) [11:29:45:593]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBCF6.tmp, Entrypoint: ExecNetFx
MSI (s) (80:EC) [11:29:45:662]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBD83.tmp, Entrypoint: ExecNetFx
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ConsoleFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Foundation.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.Controls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ViewFramework.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.WpfViews.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\Microsoft.EnterpriseManagement.UI.ExtendedControls.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorAPIInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "E:\Program Files\Microsoft System Center 2012\Service Manager\CommunicatorPrivateInterop.dll" /queue:1
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe install "Microsoft.EnterpriseManagement.Core, Version=7.0.5000.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" /queue:2
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
ExecNetFx: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe update /queue
ExecNetFx: Microsoft (R) CLR Native Image Generator - Version 4.0.30319.33440
ExecNetFx: Copyright (c) Microsoft Corporation. All rights reserved.
MSI (s) (80:9C) [11:29:50:885]: Invoking remote custom action. DLL: C:\Windows\Installer\MSID199.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMCFG
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMCFG
CAStartServices: Checking if service already started. OMCFG
CAStartServices: Attempting to start service. OMCFG
ConfigureSDKConfigService: CAStartServices succeeded!. OMCFG
MSI (s) (80:F4) [11:30:01:168]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIF733.tmp, Entrypoint: ConfigureSDKConfigService
ConfigureSDKConfigService: Custom action data property value. 1 OMSDK
ConfigureSDKConfigService: RHS so start services. 1
CAStartServices: CAStartServices was passed . OMSDK
CAStartServices: Attempting to start service. OMSDK
MSI (s) (80:A0) [11:30:04:965]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI82C.tmp, Entrypoint: WaitForSDKServiceStart
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI82C.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart
WaitForSDKServiceStart:Entering
WaitForSDKServiceStart: Error: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection.,
Stack:    at Microsoft.EnterpriseManagement.Common.Internal.ExceptionHandlers.HandleChannelExceptions(Exception ex)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.CreateEndpoint(EnterpriseManagementConnectionSettings connectionSettings, SdkChannelObject`1 channelObjectDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.ConstructEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore clientCallback)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.RetrieveEnterpriseManagementGroupInternal(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.Common.Internal.SdkDataLayerProxyCore.Connect(EnterpriseManagementConnectionSettings connectionSettings, ClientDataAccessCore callbackDispatcherService)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.InternalInitialize(EnterpriseManagementConnectionSettings connectionSettings, EnterpriseManagementGroupInternal internalsProxy)
   at Microsoft.EnterpriseManagement.EnterpriseManagementGroup.Connect(EnterpriseManagementConnectionSettings connectionSettings)
   at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.WaitForSDKServiceStart(Session session)
MSI (s) (80:A0) [11:30:36:809]: NOTE: custom action _WaitForSDKServiceStart unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
CustomAction _WaitForSDKServiceStart returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (80:88) [11:30:37:805]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1156471542,LangId=0,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (80:88) [11:30:37:805]: Executing op: DialogInfo(Type=0,Argument=0)
MSI (s) (80:88) [11:30:37:806]: Executing op: DialogInfo(Type=1,Argument=Microsoft System Center 2012 - Service Manager)
MSI (s) (80:88) [11:30:37:807]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ea.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835eb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ec.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ed.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ee.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ef.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f0.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f1.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f2.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f3.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f4.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f5.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f6.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f7.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f8.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835f9.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fa.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fb.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fc.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fd.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835fe.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\88835ff.rbf)
MSI (s) (80:88) [11:30:37:807]: Executing op: RegisterBackupFile(File=E:\Config.Msi\8883600.rbf)
MSI (s) (80:88) [11:30:40:009]: Executing op: ActionStart(Name=_Rollback_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:40:013]: Executing op: ProductInfo(ProductKey={79A76AB5-3EA0-4C4F-89B9-1CA00438EC2E},ProductName=Microsoft System Center 2012 - Service Manager,PackageName=SM.msi,Language=0,Version=117771097,Assignment=1,ObsoleteArg=0,ProductIcon=ServiceManager.ico,,PackageCode={1B3B79AF-1391-4E6E-9BE2-2BD0832DADE7},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (80:88) [11:30:40:029]: Executing op: CustomActionRollback(Action=_Rollback_RegisterVssExpressWriterSM,ActionType=1345,Source=BinaryData,Target=RemoveVssExpressWriterSM,)
MSI (s) (80:EC) [11:30:40:772]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI920E.tmp, Entrypoint: RemoveVssExpressWriterSM
CAPACK: Extracting custom action to temporary directory: C:\Windows\Installer\MSI920E.tmp-\
CAPACK: CLR version v2.0.50727 is installed.
CAPACK: CLR version v2.0.50727 is detected.
CAPACK: CLR version v4.0.30319 is installed.
CAPACK: CLR version v4.0.30319 is detected.
CAPACK: Binding to CLR version v2.0.50727
Calling custom action CAManaged!Microsoft.MOMv3.Setup.VssWriterCAs.RemoveVssExpressWriterSM
RemoveVssExpressWriter: Unregistering VSS express writer.
MSI (s) (80:EC) [11:30:43:808]: NOTE: custom action _Rollback_RegisterVssExpressWriterSM unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
RemoveVssExpressWriter: VSS express writer unregister succeeded.
MSI (s) (80:88) [11:30:43:834]: Executing op: ActionStart(Name=_RegisterVssExpressWriterSM,,)
MSI (s) (80:88) [11:30:43:853]: Executing op: ActionStart(Name=_EnabledDiscoveryDataAuthorization,,)
MSI (s) (80:88) [11:30:43:862]: Executing op: ActionStart(Name=PublishProduct,Description=Publishing product information,)
MSI (s) (80:88) [11:30:43:892]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:898]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:910]: Executing op: RegRemoveValue(Name=LastUsedSource,Value=#%n;1;E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:43:916]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:925]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:930]: Executing op: RegRemoveValue(Name=Clients,Value=[~]:,)
MSI (s) (80:88) [11:30:43:937]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:944]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,SecurityDescriptor=BinaryData,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:951]: Executing op: RegRemoveValue(Name=1,Value=;,)
MSI (s) (80:88) [11:30:43:959]: Executing op: RegCreateKey()
MSI (s) (80:88) [11:30:43:980]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media,,BinaryType=1,,)
MSI (s) (80:88) [11:30:43:986]: Executing op: RegRemoveValue(Name=DiskPrompt,Value=Please Insert Disk 1,)
MSI (s) (80:88) [11:30:43:994]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:43:994]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Media 3: 2
MSI (s) (80:88) [11:30:43:999]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net,,BinaryType=1,,)
MSI (s) (80:88) [11:30:44:005]: Executing op: RegRemoveValue(Name=1,Value=#%E:\SCSM2012sp1\amd64\Setup\Server\,)
MSI (s) (80:88) [11:30:44:011]: Executing op: RegRemoveKey()
MSI (s) (80:88) [11:30:44:011]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList\Net 3: 2
MSI (s) (80:88) [11:30:44:017]: Executing op: RegOpenKey(Root=-2147483646,Key=Software\Classes\Installer\Products\5BA67A970AE3F4C4989BC10A4083CEE2\SourceList,,BinaryType=1,,)

Remote managment Exchange 2013 SP1 from C# code using Power-Shell.

Hello,
Sorry if I am describing something wrong, but it is first time I am using Microsoft development forum.
I am trying to built library that will manage Exchange remotely using C# code (VS 2012) and Power-Shell ver.4.0. My workstation and the actual Exchange server physically placed in different domains. In order to test functionalities I am using
user that is member of all administrating and management groups in the appropriative domain. Remote Power-Shell is enabled on Exchange.
In order to connect to the Service I am using that part of code :
internal static bool RedirectionUrlValidationCallback(string redirectionUrl)
bool result = false;
var redirectionUri = new Uri(redirectionUrl);
if (redirectionUri.Scheme.Equals("https"))
result = true;
return result;
internal static ExchangeService ConnectToService(ExchangeVersion version,
string userName,
string emailAddress,
string password,
string domainName,
ref Uri autodiscoverUrl)
ExchangeService service;
try
service = new ExchangeService(version);
service.Credentials = new WebCredentials(userName, password, domainName);
if (autodiscoverUrl.IsNull())
var ads = new AutodiscoverService();
// Enable tracing.
ads.TraceEnabled = true;
// Set the credentials.
ads.Credentials = service.Credentials;
// Prevent the AutodiscoverService from looking in the local Active Directory
// for the Exchange Web Services Services SCP.
ads.EnableScpLookup = false;
// Specify a redirection URL validation
//callback that returns true for valid URLs.
ads.RedirectionUrlValidationCallback = RedirectionUrlValidationCallback;
// Get the Exchange Web Services URL for the user’s mailbox.
var response = ads.GetUserSettings(emailAddress, UserSettingName.InternalEwsUrl);
// Extract the Exchange Web Services URL from the response.
autodiscoverUrl = new Uri(response.Settings[UserSettingName.InternalEwsUrl].ToString());
// Update Service Url
service.Url = autodiscoverUrl;
else
service.Url = autodiscoverUrl;
catch (FormatException fe) // The user principal name(email) is in a bad format. UPN format is needed.
LoggingFactory.LogException(fe);
return null;
catch (AutodiscoverLocalException ale)
LoggingFactory.LogException(ale);
return null;
catch (Exception e)
LoggingFactory.LogException(e);
return null;
return service;
Then I am trying to reach existing mailbox of that user, using this part of code :
try
var runSpace = getRunspace();
var pwShell = PowerShell.Create();
pwShell.Runspace = runSpace;
var command = new PSCommand();
command.AddCommand("Get-Mailbox");
command.AddParameter("Identity", userPrincipalName);
command.AddParameter("RecipientTypeDetails", recipientType);
pwShell.Commands = command;
var result = pwShell.Invoke();
if (result.IsNotNull() && result.Any())
// TODO : fill appropriative DTO and return it.
else
// TODO : send back appropriative error.
closeRunSpace(runSpace);
catch (Exception e)
// TODO : log the exception and send back appropriative error.
private Runspace getRunspace()
var runSpaceConfig = RunspaceConfiguration.Create();
var runSpace = RunspaceFactory.CreateRunspace(runSpaceConfig);
PSSnapInException snapEx;
var psInfo = runSpaceConfig.AddPSSnapIn("Microsoft.Exchange.Management.PowerShell.E2010", out snapEx);
runSpace.Open();
return runSpace;
private void closeRunSpace(Runspace runSpace)
runSpace.Close();
runSpace.Dispose();
With this part I had problem. I received exception that appropriative Snap-in is not installed on my computer. I had no installation disk of Exchange in order to install Management Tool (as I understand this is the way to add needed part) so I changed run
space activation to that part of code :
private Runspace getRunspace()
var newCredentials = (PSCredential)null;
var connectionInfo = new WSManConnectionInfo(new Uri("http://exchange.domainname.local/powershell?serializationLevel=Full"),
"http://schemas.microsoft.com/powershell/Microsoft.Exchange",
newCredentials);
connectionInfo.AuthenticationMechanism = AuthenticationMechanism.Kerberos;
var runSpace = RunspaceFactory.CreateRunspace(connectionInfo);
runSpace.Open();
return runSpace;
Now I am receiving exception :
"Connecting to remote server exchange.domainname.local failed with the following error message :
[ClientAccessServer=exchange,BackEndServer=exchange.domainname.local,RequestId=....,TimeStamp=...]
Access is denied. For more information, see the about_Remote_Troubleshooting Help topic."
Please help me to understand what I am doing wrong.
Thank you.
Alexander.

In Exchange 2010 you should be using Remote Powershell not local powershell and the snap-in. Here is a sample that may help you:
http://blogs.msdn.com/b/dvespa/archive/2009/10/22/how-to-call-exchange-2010-cmdlet-s-using-remote-powershell-in-code.aspx

Is it possible to deploy 2 SCOM 2012 R2 reporting in a SQL server which already has SCOM reporting of a different management group but with 2 different reporting instance.

Hi Experts,
I have a typical situation in the LAB environment. Hope some one helps. I have Installed a SCOM 2012 R2 with SQL 2012 SP1 in a single server (Management group 1). I have installed another management group on another server using this SQL server for its database
so i have everything going fine.
The first management group has its reporting installed in the SQL server. For the second i created a new named instance for that. But i cannot run the SCOM setup in the SQL server (Also holding the Management group 1 MS) as 1 st reporting is already there.
When i run the setup it is asking me to repair it. I don't get the install option so i can install the reporting for management group 2 in the named instance.
Default instance is being used by the 1st management group.
Can any one figure a possibility for installing 2 SCOM reporting services for different management groups in a same SQL 2012 server please.
Gautam.75801

Hi Yan Li,
Thank you for the reply. So as you are aware If i need to instal reporting, i need to run the SCOM 2012 R2 setup in the SQL server and select reporting and select the
instance and then mention the management server there right. I am not getting that option there it is asking me to remove or repair the existing installation as there is already a SCOM entire setup including reporting there. As it is a lab there is no problem
in testing. I have 2 reporting instances. Any suggestions for me on how to overcome this issue and deploy the second reporting in the new named instance ?
Below is the screenshot of the error what i am talking about when i run SCOM 2012 R2 setup to install reporting in the SQL server
When i click on add feature reporting is greyed out (As already 1st management groups reporting is installed)
When i click on remove or repair it
uninstalls the existing one. But i want both SCOM 2012 r2 reporting to be there(For both Management group). Is it possible ? If yes What is the trick to run the setup ?
Gautam.75801

Monitoring servers in SCOM 2012 via different locals within the same management group

Hi,
I have 2 management servers in a same management group. The 1st one is having English (US) locale while other is installed on Swedish locale. Both are accessed by different users having same admin rights.
Once a USER 1 try to register a server through authoring tab from 1st management server(installed on English locale), a profile/group wrt the server registered is created successfully but the USER on 2nd management server (installed on Swedish locale) can
not see the same in Authoring tab. He can view it in Monitoring tab as as well as Administration tab.
The Vice versa is also true.
Does any one have idea that is it SCOM 2012's expected behaviour wrt 2 2 different users on 2 different locales within a same management group ?
Thanks in advance.

Hi,
I am a little confused, what do you mean by "register a server through authoring tab"?
Do you mean that when you discover a server on 1st MS with discovery wizard then you cannot see it on 2nd MS(and the vice versa)?
As far as I know, all those information should be stored in the operation database which is shared to both MSs within the same management group.
We may use SQL query to find the discovered server on the operation database. Please also check operation manager event logs to get more information to troubleshoot this issue.
Regards,
Yan Li
Regards, Yan Li

Server 2012 R2 - Remote Management Exception - Not working 100%

So,
I am spinning up a ton of VM's for the University I work at in preparation for migrating to 2012 completely and I discovered something interesting today.
The "Allow Remote Management from these subnets" option, only partially enables remote management. You still need to run the remote management enablement with NetSh (http://blogs.technet.com/b/askds/archive/2008/06/05/how-to-enable-remote-administration-of-server-core-via-mmc-using-netsh.aspx)
for the certain functionality (Remote Firewall, VDS, FRS Options), which to me seems really weird.
Has anyone else experienced this?
----------------------------------------- Dan Sheppard

Hi Dan,
If you want to manage remote server core with MMC (Microsoft Management Console), we need to configure Windows Firewall firstly to allow MMC snap-in(s) to connect on the remote server core, since your servers are Server 2012 and newer, so we can also use
the powershell cmdlet instead of cmd netsh:
Enable-NetFirewallRule -DisplayGroup "Remote Service Management"
In addition, you can also use Windows Powershell to help you to remote access with Powershell Remoting, Powershell has substantial Modules and Cmdlets to help us to manage server.
For more detailed information to manage server core, please refer to this article:
Manage a Server Core Server
If there is anything else regarding this issue, please feel free to post back.
If you have any feedback on our support, please click here.
Best Regards,
Anna Wang
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

11.3.1 remote manage group issues

Similar Messages

Maybe you are looking for