El conocimiento al alcance de todos.

Thanks to:  https://www.prajwaldesai.com/ In this post we will use group policy to configure the legal notices on the domain computers. It is possible to configure Windows Server to display a message to users when they log on. When you configure legal notice, the legal notice message appears when the user hits CTRL+ALT+DEL. While I was working as system admin, I got the task to configure a logon banner. This was for  Windows Server 2008 R2  and I am sure the steps covered in this post should work with next versions of server releases. Most of all you can configure legal notices on domain computers in two ways :- You can write a fancy script and execute it at the every logon Configure legal notice using a group policy. In my opinion the second method is very easy. You can use the message display functionality to personalize the logon process, provide news or  information , and for other similar purposes. The message appears after the user presses CTRL+ALT+DEL and disappears

Thanks to:  https://www.prajwaldesai.com/ In this post I will show you the steps to modify the Group Policy refresh interval for windows computers. By default the GP refresh interval is 90 minutes. This steps covered in this post is especially relevant to system admins. However if you want to change or modify this refresh interval time then you can do it via  group policy . The policy setting to change the group policy refresh interval time is available for both users and computers. You don’t have to configure it both rather you can modify just one of them. I am talking about the policy setting “ Set Group Policy refresh interval for computers “. This policy setting specifies how often Group Policy for computers is updated while the computer is in use (in the background). This setting also specifies a background update rate only for Group Policies in the Computer Configuration folder. The  Group Policy refresh interval  for computers policy also lets you specify how much the a

Thanks to:  https://oddytee.wordpress.com/ Lately, it seems as if I run across some new issue or anomaly on a weekly basis after implementing Exchange 2016 for one customer or another. It’s quite frustrating but it does wonders for building a personal knowledge base. One of the latest issues I’ve experienced has been with an Outlook client (2010 or newer) not connecting to a mailbox that has been moved to (or even newly created in) Exchange 2016. What’s odd to me is that this experience is inconsistent with other mailboxes that were previously moved to Exchange 2016 and Outlook is connecting without issue. Essentially what happens after an existing mailbox has been moved to Exchange 2016 and the Outlook client is restarted, the autoconfiguration process fails during the “Log on to server” task. As a result, Outlook is never able to attach to the mailbox on Exchange 2016 or update the existing profile. And, unfortunately, during the Outlook profile reconfiguration, the op

Thanks to:  https://www.networkstraining.com/ Step1:  Connect to the firewall using a console cable Step2:  Power cycle the appliance (power off and then on) Step3:  Press the Escape key to enter ROMMON mode Step4:  Use  confreg  command to change the configuration register to 0x41 rommon #1>  confreg 0x41 Step5:   Configure the security appliance to ignore the startup configuration. rommon #2>  confreg The ASA firewall will display the current configuration register value and boot parameters and ask you if you want to change them Current Configuration Register: 0x00000041 Configuration Summary: boot default image from Flash ignore system configuration Do you wish to change this configuration? y/n [n]:  y Step6:  At the prompt enter Y to change the parameters. Step7:  Accept the default values for all settings (at the prompt enter Y) Step8:  Reload the ASA appliance by entering the following command rommon #3>  boot The firewall will rebo