El conocimiento al alcance de todos.

 Thank to: https://practical365.com/ When  Exchange Server 2016 is installed  it creates a mailbox database for you on the server . If you installed Exchange to the default path then the mailbox will be stored in  C:\Program Files\Microsoft\Exchange Server\V15\Mailbox . Here’s an example from my test server: [PS] C:\>Get-MailboxDatabase | fl Name,EdbFilePath,LogFolderPath Name : Mailbox Database 2116642217 EdbFilePath : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 2116642217\Mailbox Database 2116642217.edb LogFolderPath : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 2116642217 The default location is probably not suitable for your environment, so you would likely want to move this database to the volumes that you’ve provisioned for your Exchange database and log files. Another common scenario is that the database is growing and the current volume is low on free disk space, so you want to move it to new, larger volume.

 Thank to: https://eskonr.com/ I was trying to setup new Configuration Manager 2012 SP1 build on Windows server 2012 with SQL Server 2012 SP1 installed .Everything went fine except Windows server update services .It keeps saying error with restart needed.Here is what i got every time when i install WSUS after restart the server. Update: You can also refer the solution posted here :  http://blogs.technet.com/b/heyscriptingguy/archive/2013/04/15/installing-wsus-on-windows-server-2012.aspx The request to add or remove features on the specified server failed. the operation cannot be completed because the server that you specified requires a restart.   Why does it fail every time though server is restarted several times after the error appear in the above screen ? How do we troubleshoot this ? Go to event viewer ,windows logs->system ,you see below error message: The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured passwor

 Thank to: https://www.urtech.ca/ We have worked with  Windows Server Update Services  since its inception in early 2000’s and while it is a very handy tool to manage patching, it does have several recurring problems. One of those common WSUS problems is the dreaded: RESET SERVER NODE. In addition to running the WSUS SERVER CLEAN UP WIZZARD and  scripts that clean up the WSUS SQL database , the more common fix is to adjust the Application Pool settings in IIS: How To Fix WSUS: ERROR CONNECTION ERROR: RESET SERVER NODE Click START and type IIS Expand your server Expand APPLICATION POOLS Click on WSUSPOOL and select ADVANCED SETTINGS from the action pane on the right Scroll down and set PRIVATE MEMORY LIMIT to a higher limit (I doubled mine) Set REGULAR TIME INTERVAL to a lower limit (I set mine to about half so it automatically cycles more often) Click OK on the ADVANCED SETTING dialog Right click on WSUSPOOL and select START Click RESET SERVER NODE or restart the server and have a nice