As part of an installation process, I need to enable application server role. To achieve this I need to do this. I am able to easily execute dism.exe from a C # application and can easily do it on Windows Server 2012. Here is the order that is executed.
dism / online / enable-feature / feature_name: application-server / featurename: as-nET-framework / featureName: as-ent-services / featureName: AS-DIST-transaction / feature- N: AS-incoming-trance / feature-nm: AS-outgoing-trans
But when I try to do this on Windows 2008 R2 server or Windows 7, it shows that DISM does not recognize these features. If I run commands to list the features on these machines then they are not actually available. Even if I manually enable the application server role by using the role manager and lists the features available in the DISM, then they are not listed under a different name or nothing that the application server Represent the roll.
How can I activate the program on a Windows Server 2008 R2 Server and Windows 7 application server role using C #? The solution does not have to use the DISM. I'm looking for any option.
So it turns out that even if the server manager gets annihilated in Windows 2008, you still have roles I can use it to enable the command here I used to enable it:
ServerManagerCmd -installAnti-ServicesAs-District-Transaction as Application-Server AS-incoming-trans AS-outgoing-trans
You will get the following warning but it works .
The servermates prefer CMD.exe, and are not guaranteed to be supported in the future release of Windows. We recommend that you use the Windows PowerShell cmdlets that are available for server managers.
How do you enable it in Windows 7? You can not do this because these clients are operating systems and these roles are not present. But eventually to establish this role was to establish and configure distributed transactions. Turns on Windows 7 that a distributed transaction coordinator is already available and you have to configure it.
No comments:
Post a Comment