Remote Desktop Service activation of Office Pro Plus 2013

The Activation of Office Pro Plus 2013 is not "sticking" in a 2008 R2 RDP Session. Office Pro Plus 2013 is installed on the RDS Host. Users authorized to access via their Office 365 Pro Plus Subscriptions.
Office Pro+ 2013 is installed and activated with appropriate MAK. Every few days or so a handful of RDS users are requested to activate the Office they are using during their sessions.
Any guidance would be phenomenal!
Thanks
-Patrick

you can refer to this blog:
http://technet.microsoft.com/en-us/library/dn782858(v=office.15).aspx

Similar Messages

Process msiexec.exe initiated Server restart due to complete/configure MS Office Pro Plus 2013

Hello once again, today we had a strange issue. It appears that a plugin for Office Pro Plus 2013 or indeed Office itself initiated a restart of the Remote Desktop Server it was installed on. This is obviously not an ideal situation as it ends up terminating
sessions of all users that are connected to the server.
This is the text from the Event Log:
The process msiexec.exe has initiated the restart of computer XXXXXXXXX on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x80030002
Shutdown Type: restart
Comment: The Windows Installer initiated a system restart to complete or continue the configuration of 'Microsoft Office Professional Plus 2013'.
The Event ID is 1074 / Source is User32 /
Is there a way to prevent this happening in future.

Hello Dave,
I started having the same issue on our Remote Desktop Server, Windows 2008 R2 with Office Pro Plus 2013 connecting to O365 mailboxes. The server has been set up for months and only started this behaviour. When I trawled through the logs and found
the entry you list I also checked the application log at the same time. In the Application log I found an entry with source MsiInstaller and event id 11728 detailing that an install was in progress. I could see on the Geenral TAB of this entry
that a single user had initiated this install. It should be noted that the user was not an Administrator, however they were new. When I logged on as the user and opened outlook it did come up with a window saying it was completing the install and
asked them to reboot. It does this every time you open outlook unless you open it in safemode.
I tried a number of things to fix it:
1. Disable add-ins. (No effect)
2. Reset outlook profile. (No Effect)
3. Deleted user profile from the Remote Desktop Server, renamed the relevant profile in "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList" and renamed the folder in "c:\users". (No effect)
My next step was going to be to delete the users profile completely. Before I did that I created a new test user and logged on to see if it was affecting all new users. I logged on with the user and it did not have a problem.
Strangely now when I log on as the original user having the issue the problem is gone.
I will monitor the situation, but at the moment it is fixed.
Tony
"This is the stickiest situation since sticky the stick insect got stuck on a sticky bun"

Microsoft Office Pro plus 2013 installation wizard pops up everytime I open a Word document or a new page.

Microsoft Office Pro plus 2013 installation wizard pops up everytime I open a Word document or a new page. I realize that other people have the same problem. However no answer has been found to stop this problem. I wonder if there is a
way. Hope someone is able to tell me and the others.

Hi,
By the installation wizard, do you mean the First Run screen? If yes, please follow the steps below to disable it:
STEP ONE: If you have not already, download the Office 2013 Administrative Template files. These can be downloaded from
http://www.microsoft.com/en-us/download/details.aspx?id=35554
STEP TWO: Copy the ADMX files to %systemroot%\PolicyDefinitions and the ADML files to the language specific folder (such as en-us) under %systemroot%\PolicyDefinitions.
STEP THREE: Using the Group Policy Management Editor go to User Configuration | Administrative Templates | Microsoft Office 2013 | First Run |
STEP FOUR: Set the Disable First Run Movie to Enabled and the Disable Office First Run on application boot to Enabled
Please check the result then.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs. Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Artifact for Office Picture Manager after install of Office Pro Plus 2013

Upgrading from Office 2003 to Office 2013, with the assumption that the Office 2013 install first removes all previous versions before installing.
For some users, running Windows 7, with Microsoft Office 2003 SP3 and the 2007 compatibility pack installed, after the Office 2013 Pro Plus installer runs, whenever an Office 2013 Access application is launched the user gets a message box as shown
below. None of our Access VBA have Office Picture Manager in the reference list, so it should not be an issue caused by any Access applications.
Since the Office Picture Manager is no longer part of Microsoft Office as of Office 2013, this is a problem. Several workarounds have been posted on several blogs on the Internet for installing Office Picture Manager from an earlier version on a computer
with Office 2013 installed to eliminate the error, which of course assumes that it is desireable to have Office Picture Manager.
My position is that there should be a fix for the orphaned artifacts calling for Office Picture Manager when launching Office 2013 MS Access, that does not involve the installation of a deprecated product. Multiple searches of TechNet come up empty
in that regard.
Is there a fix for this issue forthcoming, or does anyone have an answer that does not involve installing a backrevved Office Picture Manager just to make the error message shut up?
Clean install of the OS is not to be considered a solution. There are too many computers involved to even consider that to be acceptable. I would rather have a registry cleanup script that could be pushed through GPO than to have to go to each
computer and run a FixIt, so please try not to push the FixIt option either...
Thanks!

Always, the in-place upgrade doesn't remove all traces of Office 2003 from your computer, and this will cause unexpected issues for the new Office.
Actually, instead of doing a in-place upgrade, you can perform an
uninstall-upgrade to Office 2013. When uninstall the old version of Office 2003, you can make sure to remove any traces, and then install the new Office 2013.
For how to do an uninstall-upgrade, you can refer to this blog post:
http://blogs.technet.com/b/odsupport/archive/2011/04/06/how-to-perform-an-uninstall-upgrade-to-office-2010.aspx

Brand new Surface Pro 3 with Office Prof Plus 2013

Just purchased today and brought home a brand new Surface Pro 3.
The first thing I needed for work, Office, and so I started to install, via USB DVD drive, the program Office Professional Plus 2013 - the fully loaded flagship version of Office that I purchased in March of 2014.
I was shocked that I am unable to install it. I first tried installing the 64-Bit Office version, since Windows 8.1 is 64-bit. Next I learned that I must uninstall the 32-bit trial versions of Office that came pre-loaded onto the Surface Pro 3. I even used
the Microsoft Office Fixit utilities and the Support descriptions of manual removal of previous versions of Office.Resetting the Surface Pro 3, uninstalling all Office products from it, and installing as 32-bit did not help either.
The errors I see are not describable, because nothing happens, the install just hangs with no messages. The machine keeps operating fine, but the Office installs do not work at all.
All of these efforts have only led to frustration.It appears to me that the flagship 2014 Surface Pro 3 and the Office Professional Plus 2013 (purchased only this Spring) are incompatible. This came as a great shock for me because in all my history of installing
current MS software on current systems, I have never had this problem. Maybe back in the days of Windows 3.1 it might have happened. Please, if anyone has any advice , please advise.

Thanks Melon Chen for your quick and helpful reply. Somehow (I will explain below), I was at last able to install the Office 2013 Pro Plus Suite.
Before I received your reply with detailed instructions I kept trying many other solutions .. eventually I made Office 2013 Pro Plus install, although I'm not exactly sure what ended up fixing my ability to install from DVD.
here's what I did:
1) I attempted to install Office 2013 Pro Plus after running Fixit Utility and again the clean boot, but those did not help. I received the same error message that I described (ie. no specific error coded message, only a message that Office 2013 Pro
Plus failed to install. After rebooting with the "clean" reset option , I noticed there was some of my personal setup information retained on the system (can't recall exactly what this was , but it was clear to me that the reset
did not make my system in pristine factory image). I discovered an even cleaner reset is the following to reset the Surface Pro 3 'absolutely' to factory image using a downloaded factory recovery image that is available here:
-->
http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/downloadablerecoveryimage?lc=1033
This also required creating a USB drive based install and this reset the Surface Pro 3 to factory condition as described here:
-->
https://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/usbrecovery
Now, after all this, regarding the Office Pro Plus 2013 install, 64-bit, it failed yet again, but one good thing was that the error message stated something different ie containing the text
" Background installation ran into a problem. ... We'll automatically resume...." . With this information, I explored the internet over the weekend and I found the following valuable site on the web:
http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/unable-to-install-office-2013-error-codes-30102-1/fde35d75-bddc-4dd6-bd0a-e01d07420f49
Although I did not observe the error codes (apparently, it is explained that MS has stopped showing many error codes) as depicted, but the symptoms were identical. And so reading the link, there was one user , Rohn007, who compiled a beautiful listing of this
problem of installing Office 2013 Pro with suggested solutions; lo and behold, the solution describing
multiple wireless devices seemed to solve the problem. In other words, by being a heavy MS early-adopter, during Office 2013 Pro Plus install, I had a couple of MS devices, like Lumia phone, pc, etc.. all linked to the same wireless router
during my attempts to install to the Surface Pro 3. I have only a single MSN user ID and password for all the devices. I could be wrong, but this situation with shared wireless apparently can mess up the installs of Office 2013 Pro Plus- but often it
is disguised and murky because no error codes are generated. By turning off all the wireless connections except for the one connecting to the Surface Pro 3, I was AT LAST ABLE TO INSTALL OFFICE 2013.
In the end, I installed Office 2013 32 bit, but I really wanted 64 bit. I will try now and uninstall everything again. and then go for the 64 bit version.
I was very worn out by this experience. A full 2 days trying to install a brand new Office 2013 onto the brand new Surface Pro 3 with Win 8.1 apparently all came down to the fact maybe that I had too many wireless connections going! In the end I am
happy that I can finally discover this beautiful piece of hardware, but I am a bit scared since I also would like to install Adobe CS4 from DVD drive and I am worried that I will again have much trouble. Do you have any suggestions when installing the Adobe
CS 4 Master Collection, are there suggested steps to take? I like the idea of running Event Viewer, do you think that cab be helpful during installs.

Licencing Office 365 on Remote Desktop Services

So I am looking to move to Office 365 in the near future instead of just renewing my SA against Office standard.
I read somewhere that in order to continue to be able to clone these installs as part of my Terminal Server rollout, I need to purchase at least on Office licence on SA.
This is to allows access to the .ISO file and KMS licence. To keep compliant, the rest I will purchase via Office 365.
Does that sound about right and can I use Office 365 Mid Business as the version or does it have to be Pro?

I read somewhere that in order to continue to be able to clone these installs as part of my Terminal Server rollout, I need to purchase at least on Office licence on SA.
This is to allows access to the .ISO file and KMS licence. To keep compliant, the rest I will purchase via Office 365.
I'm not quite sure what do you mean by "clone these installs as part of my Terminal Serverl...". If you mean use Remote Desktop Services (RDS) to provide shared computers to users in your organization, you can use
shared computer activation to do this.
Please note, you have to do this with
Office Deployment Tool. Here is the reference you'll need:
http://blogs.technet.com/b/uspartner_ts2team/archive/2014/09/03/office-365-shared-computer-activation.aspx
http://technet.microsoft.com/en-us/library/dn782858(v=office.15).aspx
Office 365 has nothing to do with .ISO file and KMS licence. It uses Click-to-Run as the new installation technology, and must be activated with the Microsoft account associated with your subscription.
Regards,
Ethan Hua
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Windows 2012 R2 Active Directory Domain Services and Remote Desktop services Role on the same server.

Findings:
Currently, Windows 2012 R2 AD DS role and RDS With Broker services can only seem to coexist properly in a new domain not an existing domain. Any attempt to add to an existing domain causes internal database user access denied issues and any attempt to
adjust rights and circumvent is dubious at best.
The escalation technician said it best. Out of 50 clients that want to do this, they end up not being able to help 5 right off the bat for whatever reason. As for the other 40 they might be able to help by running reports, adjusting rights and trying to add
the roles until it works. This can end up being a 20 day process. Basically they are playing whack-a-mole with user rights and permissions until something sticks.
We tried creating an OU where any other domain policies would not be inherited to see if that was the issue, a fresh install with different sequence of adding the Roles, no effect.
Given the errors I witnessed when running procmon and then trying to add the roles, the NT System and the Windows Internal database user had access denied issues on 100+ registry keys when trying to add the roles. After that the system is not behaving normally.
The errors displayed almost mirror the errors that would occur on Windows 2012 when those two roles would be added which of course is officially NOT supported on that system.
This blog needs serious revision:
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
This is the excerpt from that blog: Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker.
Microsoft Support was curteous and helpful and they were the ones who advised cutting our losses, which mirrored my hunch after seeing what was transpiring in the system. They refunded my money for the support call.
For me, it was an opportunity to find out if there was any way to configure Windows 2012 R2 in the Same manner that it was setup as Windows 2008 R2 and lay that to rest. The coexistence is poorly implemented. It is as if there was a reaction from all the deprecation
of bread and butter features such as shadowing in TS and the coexistence of AD DS and RDS to where those features were re-added haphazardly. (I have no complaints on shadowing on Windows 2012 R2 it works, just do not like having to go to server manager to
use it).
I opted for virtualizing the Domain controller to eliminate the incompatibility issues and that is what I will be doing from now on. I found free solutions for backing up and reporting for virtual machines as well as the suggested procedures for configruing
a Domain controller as a virtual machine on a Hyper-V environment and I will be sticking to those. Thus far the setup has been operational.
I am not allergic to virtualization, but for really small setups it adds additional time and considerations but if that is how it has to be done, so be it. Windows 2008 R2 days are numbered and since we can usually squeeze 5-7 years on quality server equipment,
buying a Windows 2008 R2 setup now is a borderline disservice in my opinion.
Hopefully someone finds this useful and saves some time.

Hi,
Thank you for posting in Windows Server Forum.
Do you need any other assistance?
Based on your description, you are describing your story of successfully implementing RDS server with AD role and more regarding all RDS related scenario. For shadowing feature, you can use with command also. Below is the syntax to shadow a session.
mstsc /v:<ServerName> /shadow:<SessionID>
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Using unattend install files to automate the creation of Win7 pooled VDIs in 2012 remote desktop services

Hi All,
I have a problem that I have been working on for the past week and hoping someone can provide the missing link for me.
Background
We currently have a 2008 "VDI" environment with both personal and pooled Windows 7 desktops deployed to thin clients. We have just set up our first 2012 Hyper-V server and plan to deploy pooled and personal VDIs under 2012. I have been working
on the process and successfully created both pooled and personal Windows 7 desktops using the Remote Desktop Services and creating the collections.
I created the golden image and sysprep'd it (/Generalize /OOBE /Shutdown). During the creation of the Pool collection I manually inputted the Virtual settings (i.e. the OU, etc). I notice there is an option to supply an unattend.xml file with the answers.
We are deploying the pool into a computer lab in the school for the students to use. I want the pool to revert to the pristine state after the student logs off.
Problem
When the user logs into the pooled desktop I notice that the activation for the Windows license has not been run. I am trying to use the unattend file to activate the license before the first log-in. Using the Windows System Image Maker I've install our
volume license key, but it does not activate. The only option I have to activate it is to run a synchronous command during first login. This can only be inserted in the OOBE phase. When the user logs in the license activates, but when they log out,
the machine reverts to the pristine state.
I confess I'm newbie to unattend installs but I've been reading the docs on line trying to figure out how to change this behavior. I'm also assuming this won't be a problem with the personal desktops pools.
Any help is greatly appreciated.

Hi,
Please make sure to following guide like this link to deploy the virtual desktops
Windows 8 / Windows Server 2012: Pooled Virtual Desktop Infrastructure
http://blogs.technet.com/b/askperf/archive/2012/10/31/windows-8-windows-server-2012-pooled-virtual-desktop-infrastructure.aspx
Regarding to activation, see introduction in this link:
http://technet.microsoft.com/en-us/library/dn645522.aspx
Which did you use? for KMS as an example, you have to activate the master\template VM with the Windows version specific KMS Key and make sure that your KMS Server is auto discoverable.
The snapshot on the automatically created pooled collection VM is taken before KMS activation is initiated from the guest OS. So the KMS activation would take place only after user logs on. once the rollback is enabled, the pooled VM will
rollback to clean state and may perform the windows activation again when any user logs on to the VM again.
And you mentioned that you're using WSIM and installed Volume License Key, (I suppose you mean that you've typed the key in the "Product Key Selection" in WSIM), but as I know, we should leave the product key blank if you are using KMS host
for activation.
Yolanda Zhu
TechNet Community Support

Install Remote Desktop Services Failed on Windows 2012 Server

I understand RDS is not recommended on DC due to security consideration. However since I want to play it at home, it is not much a concern. Such scenario works fine on Windows 2008 R2. But on Windows 2012, the RDS (session-based, have not
tried VDI, but expect same result) installation always fails and is incomplete on DC.
In \Administrative Tools\Terminal Services, I only have RD Licensing Diagnoser and RD licensing manager. The remote desktop service management service cannot be started (Error code: 0x88250001). Is there any extra configuration needed for RDS
working on Server 2012 DC or before the installation? Thanks.
Update: this issue has been solved in Windows 2012 R2 Server. According to
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
"Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker."
The guidelines (http://support.microsoft.com/kb/2833839/en-us) primarily apply to Windows 2012 Server.

Asinine. Simply Asinine. Microsoft took it out because of $GREED$.
RemoteDesktop has become so popular, they had to break it to make more money. Thats why they discontinued SmallBusinessServer.   If this practice is so tabooo... Why did MS go the opposite direction with SBS 2011 Premium Cal's? SBS2011
had DC, Exchange, RDS and Sharepoint,SQL, RemoteWebWorkplace, OWA all working in perfect harmony. It is an untrue statement then, that it was "allowed but not recommended"
Now you by Server2012 (core + two virtual) and its not enough for all this.
You need at least another $700 for another sever licence to have it all
and who knows if SQL will run on a DC, or Exchange, or R-DERP server. Another reacherous bridge to cross.
By far, the absloute worse release since Millennium. The product is not ready for production, we broke our rule of waiting until the first SP1 upgrade for this and Exchange 2013. Problems with USB drivers and networking running extreamly slow.
Our 2003 SBS server was at least three times as fast, and this server has SAS and SSD drives running. It can't get out of its own way, and IE10 is the most unstable piece of crap to come out of Redmond. Open wide and swallow - Mother Microsoft
knows whats best for you. YOU WILL EAT OUR SLOP AND LEARN TO LIKE IT.   Server2012 AKA "METRO-SERVER"
Now here I sit after 50 Hours back to back setting up a new R-DERP server 2012, AD, Have my RDP licences in my hand at $100 each, and WTH does Microsoft care if I install it on my DC. ITS MY DC. And the cost savings versus the "risk" was
previously MY decision.
Sure, I can install a couple of Virtual HyperV sessions but they are so tempremental to a power-outage in a small business its not worth it. I have to double up my server hard drive resources, buy a $800 battery backup unit and make sure to attach
the cable, and even then, if that Bi**H does not shut down properly, one bit goes awry in a VHD or VHDX file and you are screwed. Restore from lastnights backup and forget about todays work. Not to mention it will probably take a half day to try
to fix it, then recover it then tell the 30 users they lost a days worth of work.
HYPER-V is for test servers and has no place in a small (micro) business environment. 5-30 users.
Microsoft's solution, buy another server. Need Exchange? Buy another server or take the risky cheapskate route and spin up some VHD's. Might as well put a gun to your head and play russian roulette, at least you know you have a one in six
chance of failure. With MS, its a 100% failure for a dirty shutdown power loss, motherboard blows, memory goes corrupt in a few years, your conventional method of recovery is gone, and you have some upchucked VHD file to try to recover some of TODAYS
data from.
Screw server 2012 forever.
I will sell 2008 and SBS2011 Premium unitl it rots in hell like XP (of which there is NOTHING wrong with for the average, WORD, EXCEL, OUTLOOK and QUICKBOOKS that all SMB's use. Its MS $GREED$ Grab the world by the B**ls and squeeze with all
your might to squeeze every dime you can out of *SMB* because big business is going to run thier 2003 Exchange and 2008 servers into ground before they switch to this garbage.
YOU CANNOT INSTALL EXCHANGE 2013 on DC , OR on R-DERP server.
Go buy another server license and server or MOVE TO THE CLOUD and get fleeced every month.
I have 30 DC/R-DERP/Exchange and SBS2011 Premium servers all running for years in perfect harmony, locked down with security so the users can't even WIGGLE with something they are not supposed to work with. They get their apps, cannot install anything
and all these servers are running just fine behind the firewall and perfectly save. The track record of this combination is 100% stable and is up 24/7/365 with no problems. Do yourself a favor and throw this 2012 into the river, you don't need
any weights because it is LEAD and will sink to the bottom by itself.
Why, you ask? Official is "Its for your protection" The real reason? To sell you more $700 server licences.
Maybe for SMB, we start selling Linux NAS Servers, host the Exchange in the cloud and be hearded like cattle to the Microsoft slaughterhouse. One way or another, you are going to bleed.    A little each month to move to the cloud, or
a small fortune if you want to have it in house. Microsoft wants it to be more expensive to have in house. No more buying a server and running it for six years before you upgrade. They can't have in house servers competing with their cloud,
and small businesses are the low hanging fruit ripe for the pickin'.

Questions in regards to server 2012R2 Remote desktop Service deployment and GPO

Hi Everyone
We have a business requirement moving to 2012R2 RDSH server. I have installed a 2012R2 member servers and enabled Remote desktop licensing role. I have activated the licenses. the servers is in operational
I have deployed 3 windows 2012R2 member server "RDS1" , "RDS2" and "RDS3".
on RDS1 I ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation.
On RDS1 Server Manage Dashboard Page Select Remote Desktop Services > Overview. Under RD Licensing I added my 2012R2 license server "2012r2-tslic". Go to task. Edit deployment properties RD license mode to per device and click OK.
Reboot RDS1
Check RD Licensing Diagnoser everything is clear
On RDS2 I did the exact same thing ran Add roles and Feature Wizard > Remote Desktop Services installation > Quick Start >Session based desktop deployment to complete the installation.
But With RDS2 I move this server to an OU that link to a GPO with RD licensing details. after reboot the servers check RD Licensing Diagnoser I can see 2012r2-tslic specified as the license servers.
Based on this document
http://blogs.technet.com/b/askperf/archive/2013/09/20/rd-licensing-configuration-on-windows-server-2012.aspx Are you suppose to configure RD license server via Remote desktop Service deployment ? Not GPO ?
Here are my questions
We currently have ten 2008r2 terminal servers in a NLB cluster. each RDSH server have in house application installed on each one of them. User connect to the 2008R2 RDSH servers via RDP connection. we have a restricted GPO apply to those
RDSH servers. user cannot do anything on RDSH servers apart from running the application and use excel. On the remote desktop session host configuration we have enable settings like end a disconnected session , Active session limit ,
remote control users session , LPT port redirection.
We push out RD license server detail via GPO to the terminal servers
Can I use our existing GPO apply the licensing server settings , desktop restriction setting to the 2012R2 RDHS servers or we should be using Remote desktop Service deployment to do the job ? If that is the case how would you transfer the
current 2008r2 environment to 2012 using Remote desktop Service deployment. is that mean I have to manually configure 1 by 1.
Please help
Many thanks

Hi,
Please see my response to you in the other thread. Please contact me via email and I will go over the basic planning and deployment steps with you which will help clear things up and get you started off on the right foot.
You should only run through the wizard and create a RDS deployment once. Then you add the various servers (RDSH, RD Licensing, RD Gateway, etc), set Deployment properties, etc.
Thanks.
-TP

Remote Desktop Services Error when trying to send a message to a user in the collections

We are implementing RD for thin clients and when I try to send a message to a user I get an error that states,: Unable to send a message to session X on (SERVER NAME.COM). WTS API Failed
Is there a service that needs to be turned on?
Thanks EPK

Hi,
Thank you for posting in Windows Server Forum.
Before sending message please check following considerations.
- You must have Message special access permission to send a message to a user.
- You can send messages only to users whose sessions are in the active or connected state.
- You can send a message to a user session in Remote Desktop Services Manager by using the Send Message action.
Send a Message to a User
http://technet.microsoft.com/en-us/library/cc754124.aspx
Else you can also try below script and check the result.
Send-NetMessage - Net Send / Msg.exe
http://gallery.technet.microsoft.com/scriptcenter/Send-NetMessage-Net-Send-0459d235
Hope it helps!
Thanks.
Dharmesh Solanki

Terminal Services (TS) or Remote Desktop Services (RDS) scenario clarifications

Dear Support,
Question:
Do I still need to purchase RDS CALS license? or can use MSDN CALs in the Terminal Server?
Due to MSDN subscribers are End users, do not use Production Data and have to demo their developed applications to other End users group.
Scenario:
1. Use only Remote Desktop Session.
2. End users are MSDN Subscribers. (Although stated by Microsoft End users are non MSDN subscribers)
3. End users demo applications to End users.
4. End users develop their applications and have to demo to other End users group.
From MSDN link:
Client Access Licenses for Terminal Services
With an MSDN subscription, you are allowed to provide end users access to Internet demonstrations of your programs via Terminal Services (Windows Server 2003 or Windows Server 2008) or Remote Desktop Services (Windows Server 2008 R2). Up to 200 anonymous
users can simultaneously access your demonstration this way. Your demonstration must not use production data. MSDN subscribers are licensed to demonstrate their applications to end users,
but Terminal Services (TS) or Remote Desktop Services (RDS) is the only scenario where end users without an MSDN subscription can interact with the demonstration application while the software is licensed through MSDN subscriptions.
Accessing CALs
MSDN subscribers can access CALs for demonstration purposes through the
Product keys page of MSDN Subscriber Downloads. Please access the documentation resources online for assistance with the
Terminal Server activation process. If you have any questions, please visit the Microsoft
Terminal Services forum.
Mary Lee

Hi
Please call the licensing to be sure. In the USA (866) 230-0560 or
[email protected]
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

User profile vs Remote Desktop Services Profile

On a Windows 2008 R2 Domain Controller, if you open properties of an user account, you'd see
a Profile Tab as well as Remote Desktop Services Profile Tab.
I found this very confusing, can any one tell be the key difference between those 2?
If I don't specify Remote Desktop Services Profile path, when I logon to Remote Desktop Server, it seems take user's
romaing profile.
Anyway, please advice.
Thank you.

Hi,
Thank you for posting in Windows Server Forum.
The profile tab of the user properties window allows you to configure user profile, logon scripts and home folder details for the user object. It is very useful when you have to allow your user access the same environment and data irrespective of the machine
he logs in from.
Active Directory User properties – Profile tab
Remote Desktop Services User Properties
You can specify a Remote Desktop Services-specific profile path and home folder for a user connecting to an RD Session Host server. This profile and home folder will only be used for Remote Desktop Services sessions. You should assign a separate profile for
Remote Desktop Services sessions because many of the common options that are stored in profiles, such as screen savers and animated menu affects, are not desirable when using Remote Desktop Services.
Manage User Profiles for Remote Desktop Services
http://technet.microsoft.com/en-us/library/cc742820.aspx
User Profiles on Windows Server 2008 R2 Remote Desktop Services
http://blogs.msdn.com/b/rds/archive/2009/06/02/user-profiles-on-windows-server-2008-r2-remote-desktop-services.aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Windows 2008 Remote Desktop Services - Word Spell Check

We are running Windows 2008 servers on our network with remote desktop services (terminal services). We currently experiencing a challenge with Word 2010. The spell check feature is not working, when you try and run it gives an error "Microsoft Word
can't check the spelling or grammar in this document. An error occurred and this feature is no longer functioning properly." After about 5 clicks it comes up with Cannot find the proofing tools for English (Australia). It eventually it works, need to
get it to work the first time. I have searched all around but can't seem to find the answer.

I'd try them over here.
Word
2010 forum on Microsoft Answers
Word IT Pro forum on TechNet
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Audio service hangs on Windows Server 2008R2 with Remote Desktop Services

Hello!
I have some terminal servers on Windows Server 2008R2. Users have the ability to use web browsers (IE, Firefox) with the included Flash Player, IM clients / Internet
telephony (Skype, ICQ), Windows Media Player, Office, and a specific internal software (works with MS SQL). I have the following problem: the Windows audio service hangs up that leads to hangup of all programs which use it, such as: any sites in Internet with
a flash content (in all browsers), ICQ, Skype.Even logging out the session hung when tried to lose a sound. It's impossible to stop or restart service from the services.msc the service just hang with status "restarting". To stop service I terminate svchost
process. As soon as the audio service is stopped - all programs start to work correctly (certainly without a sound). This problem appeared not suddenly - periodic hangups of programs on servers were marked long ago (more than half a year), but not directly
were connected to audio service, especially there were they rather rare (on the average once a week - two) and were corrected by server reset. The error message:
Error container , type 0
Event name: AppHangXProcB1
Reply: No data
Ident CAB: 0
Problem signature:
P1: iexplore.exe
P2: 9.0.8112.16446
P3: 4fb57c8f
P4: 77c1
P5: 131200
P6: svchost.exe:AudioClientRpc
P7: 0.0.0.0
P8:
P9:
P10:
shall suggest an idea about a sound service, but in Event Viewer has no Windows Audio events.
Recently I updated Skype to the last version 6.0.66.120. Before was 4.2.35.155 because versions 5хх on Windows2008R2 with the Remote Desctop Services actually don't
work, if users at the server more than one or two. We checked the sixth version by the test machine with the terminal environment and very were delighted to its normal working capacity. However after installation of this client on production servers it appeared
that hangups of programs on servers began to occur on the average time at an o'clock in case of an average daily load (about 20 users on one server). If you have worked one or two users, problems weren't watched. Internet search led me to the support page
Skype, where the Windows 7 x64 user faced a similar problem in the fifth version of the program. But the solutions proposed by the support team does not help me. In addition, I found the advice to disable enhancements in the properties of the playback device,
but it is impossible for the "Remote Audio" device.
At the moment, on servers where I updated the Skype, I disabled the audio service. If within a reasonable time, I do not find a solution, I will have to revert
to an older version of Skype, but I would like to solve the problem completely.

Enable the Allow audio and video playback redirection Group Policy setting
To allow audio and video playback when connecting to a computer running Windows Server 2008 R2, you must enable the Allow audio and video playback redirection Group Policy setting. The Allow audio and video playback redirection Group Policy setting is located
in Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Device and Resource Redirection and can be configured by using either Local Group Policy Editor or the Group Policy Management
Console (GPMC).
For more information about Group Policy settings for Remote Desktop Services, see the Remote Desktop Services Technical Reference (http://go.microsoft.com/fwlink/?LinkId=138134).
Is this policy applied? Refer:
http://technet.microsoft.com/en-us/library/dd759165.aspx
Also, have you tried update the audio device driver for this terminal server?

Remote Desktop Service activation of Office Pro Plus 2013

Similar Messages

Maybe you are looking for