Is there a way to turn off the automatic display of Server Manager after each log on to the server (Windows Server 2008R2)? Can I do that for all servers that are domain members?
Why not go directly to the source of what is starting Server Manager, instead of putting up roadblocks to stop it afterwards? I found it easier to simply disable the task in Task Scheduler that starts Server Manager.
This was brought to my attention at: http://flamingkeys.com/2010/09/how-to-disable-server-manager-globally-on-server-2008-rtm-or-r2/
Just open Task Scheduler and navigate to:
Task Scheduler (Local) > Task Scheduler Library > Microsoft > Windows > Server Manager
Then right-click on the task and select Disable.
Carl
You can disable this behavior, and this is done either by enabling the check-box Do not show me this console at log on or by setting a Group Policy.
If you have an Active Directory Domain Services environment, then you can set it using Group Policy Management Console.
To disable Server Manager automatic display after log on, follow these steps: In Server Manager, under the Server Summary section, enable the check-box beside “Do not show me this console at log on” and close the window.
To set it though Group Policy, then follow these steps: Go to Administrative tools then to Group policy management. In Computer Configuration for Default Domain policy (or any other policy setting e.g. for some OU), under Policies/Administrative templates/System find Server Manager and then enable “Do not display Server Manager automatically at log on”
Related
How can we force an IIS app pool to go into Unknown state? Is there a way to do this through the inetmgr GUI or through power shell ? I want to test a script that I'm writing, based off the Unknown state of my IIS app pool
As far as I know, if you log into the IIS server machine with non-admin account, then go to inetsrv folder and run "appcmd.exe list apppool" in command prompt ,you will get unkown state like below:
And before that you may need to add this non-admin user access permission to the config folder.
By the way, are you trying to test Powershell session? using "Get-IISapppool" in powershell with non-admin account will also get an empty state showing.
I have setup a azure cloud classic. Where I have two instances running one is web role and orleans silos. I want to enable trace and I need a means to login into the box and see the logs. Azure portal is not providing the logs I needed. I am following the following link https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-role-enable-remote-desktop but, in the first step, is to click on the cloud service and click configure but I do not see configure option anywhere. I see only 'Pin, swap and delete'. But I did see an option when click on the cloud class, called configuration. In that configuration, there is nothing for remote desk top.
I do have an option for remote desk top, but when I click that I get an message "This deployment is using RemoteAccess and/or RemoteForwarder modules. We recommend using the RDP extension instead. You can enable this mode by removing the modules from your .csdef and .cscfg and then saving your RDP configuration here."
so my basic question, how what is proper way to remote to that box provided I am getting above mentioned message?
According to your description, you are using Azure new portal to configure Remote Desktop. For a simple way, you could log into Azure classic portal to leverage Remote Desktop Extension approach for you to enable Remote Desktop even after your application is deployed.
Note: For more details, you could follow the section about configuring Remote Desktop from the Azure classic portal in this doc.
so my basic question, how what is proper way to remote to that box provided I am getting above mentioned message?
You could follow this tutorial about configuring Remote Desktop in the service definition file.
Background info: Automatically run data connections in XLSM
I have a batch script which logs a start and end time, and runs a VBS scripts, which in turn opens up a excel file, runs a couple of data connections and closes the file again.
This works just fine when I run the batch script. However when I run it through the task scheduler the data connections are not run on the excel file. It seems like it might be related to some sort of security issue, but I cant figure out what the issue is exactly.
In the eventviewer of the server I was setting this up I found this little message:
The machine-default permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{00024500-0000-0000-C000-000000000046} and APPID Unavailable to the
user DOMAIN\USER SID
(S-1-5-21-3431573511-3352521975-2604885492-32293) from address
LocalHost (Using LRPC) running in the application container
Unavailable SID (Unavailable). This security permission can be
modified using the Component Services administrative tool.
But I have no idea what this means.
I ran into the same issue when trying saving an Excel file via a Powershell script. I wasn't able to adjust the security settings for CLSID “000C101C-0000-0000-C000-000000000046”, which should resolve this, so I ran the task under the SYSTEM account, which already had the necessary permissions. This resolved the issue.
This error is being logged into the System event logs in Event Viewer due to inadequate permission for the farm admin account on the DCOM component 000C101C-0000-0000-C000-000000000046. In order to change the permission settings, perform the following steps:
Open Component Service by clicking Start → Administrative Tools → Component Services.
Navigate and expand the node Component Services → Computers → My Computer → DCOM Config.
Right-click the sub node “000C101C-0000-0000-C000-000000000046” and select “Properties”.
On the Properties dialog box, select Security tab. In most cases you will notice that the settings are grayed out. This is because the logged in user doesn't have enough permissions on this component to change the settings. In order to provide this permissions, perform the steps described in next section “Change Component Service Owner and Permission”. You may need to restart the server after doing this.
Once you set up the permission mentioned in previous step, in the Launch and Activation Permissions section in Security tab, select Customize option and click Edit.
In the popup window, add the farm admin user account and check Local Launch and Local Activation permissions.
Restart IIS and SP Timer. If possible, restart the server itself.
Reference: http://sajiviswam.wordpress.com/2011/04/15/the-machine-default-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-000c101c-0000-0000-c000-000000000046-sharepoint-2010/
I'm trying to connect to default web site on localhost – but IIS asks me for credentials (I know I can use an Administrator account, but I'm trying to log on when IIS is not run as an Administrator). I tried putting in the administrator user name and password for windows, but it doesn't accept them.
I'm using windows 7 home premium.
What should I enter?
ok - so anonymous is enabled. The next thing to check is that the identity the website is running under has access to the website folder. Each site in IIS runs in an application pool, and each pool runs under a user account. So first find out what app pool you're running under. On the right hand side click on Advanced Properties and check the name of you application pool. Then close that window and double click on application pools above your website on the left. Click on the app pool your site is running under, and then click advanced properties on the right. In the dialog box that launches, under process model check the value of Identity. Then go check the permissions on your website folder and make sure that identity has a minimum of read and execute rights on the folder.
Added another answer as the text above exceeds the comment limit
If you're trying to set your identity for a site to run under then you either need to run it as the local system account or you need to create a new user account on the machine and use those credentials.
I have an issue that when I deploy a simple web application with startup tasks. After deploying, when I will click on the instance, then it seems to be disabled, as shown in the image below:
Is there any specific reason for this? And how can I overcome this situation?
This whole section is all about Remote Desktop connectivity. Not the "Azure Connect". So far I have never seen the "Connect" icon disabled after successfull deployment. If you are experiencing issues make sure:
You have enabled remote desktop prior you deploy (once configured it
stays configured, unless you explicitly disable it)
Your account expiration date has not passed
Your instance is in "Ready" state
The certificate used for password encryption has not expired
Wait a couple of minutes after instance state is "Ready" - there
might be a slight delay between RDP configuration and actual
enablement
If you still have issues, try clicking on a Role, not an instance. Then the other 2 options shall be enabled (Enable & Configure). Check their status and change it, if the "Enable" checkbox is not checked. And check the "Configure" for the user account and password.