PID 4 Using Port 80 – IIS Unable To Bind

Assurdo!! MI HA FATTO IMPAZZIRE!

IIS su Windows Server 2016, porta 80 impegnata da PID 4 System!!!

eseguendo un: netstat -o -n -a |findstr 0.0:80

restituisce:

TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4

La soluzione è:

fermare è disabilitare il servizio “Windows Sync share” in italiano “Condivisione di sincronizzazione Windows”

Su Windows Server 2012 R2  Essentials ho risolto con:

netsh http add iplisten ipaddress=:: vedi anche: https://superuser.com/questions/352017/pid4-using-port-80 https://hungred.com/how-to/pid4-using-port-80-windows-server-2012-r2/

How To Activate Windows 10 / Server 2016 Through Command Line

If you are having problems activating Windows 10, Server 2016, Windows 8, or Server 2012 one of these three solutions below should get you through:

This is handy if the GUI won’t start and you want to skip some steps to get it to work.

  1. click START (gets you to the tiles)4-no-change-product-key-link-missing-dns-error-0x8007232b-dns-error-activate
  2. type RUN
  3. type slui 3 and press ENTER
    1. yes, SLUI: which stands for SOFTWARE LICENSING USER INTERFACE
      1. SLUI 1 brings up the activation status window
      2. SLUI 2 brings up the activation window
      3. SLUI 3 brings up the CHANGE PRODUCT KEY window
      4. SLUI 4 brings up the CALL MICROSOFT & MANUALLY ACTIVATE window
  4. Type in your product key
  5. Have a nice day.

  1. Launch a CMD as an Administratorcommand-line-to-activate-windows-slmgr-slui
  2. Type: slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
  3. Press Enter

If your key is valid and you are connected to the internet, it should activate within a second or two.

In Canada and the US, call the support line directly at 1 800-936-4900, otherwise, use this table of Microsoft Activation Phone Numbers to do the deed.

You also might find some of our previous posts on activation problems to be helpful:  urtech.ca/?s=activation

Non è stato possibile recapitare il messaggio in una cartella pubblica perché il recapito a questo indirizzo è limitato ai mittenti autenticati

The message could not be delivered to a public folder because the delivery to this address is limited to authenticated senders

In Exchange 2013 e Exchange 2016 occorre abilitare i permessi per gli utenti anonimi nelle Public Folder

controllare gli attuale permessi con:

Get-PublicFolder “\” -Recurse | Get-PublicFolderClientPermission | Out-File -FilePath “c:\Temp\PFPerms.txt”

Assegnare i permessi all’utente anonimo:

Get-PublicFolder “\” –Recurse | Add-PublicFolderClientPermission -User Anonymous -AccessRights “CreateItems”

fonte:http://windowsitpro.com/blog/security-design-change-office-365-public-folders-causes-inbound-email-ndr

vedi anche: https://technet.microsoft.com/en-us/library/aa997560(v=exchg.150).aspx#CreateItems

 

EXCHANGE 2016 OWA COULD NOT BE OPENED WITH FIREFOX OR CHROME BROWSER

fonte:http://www.gierth-consulting.com/blog/articles/20170222-01.html

With Microsoft Exchange Server 2016 CU4, OWA in Exchange 2016 could not be opened with Mozilla Firefox or Google Chrome browser, but it will work with IE and Microsoft Edge. Using Firefox or Chrome browser the error *NS_ERROR_NET_INADEQUATE_SECURITY’ will be displayed in the browser. The reason for this for this error is the integration of the HTTP/2-Standard in the Windows Server IIS components by Microsoft.

To fix the problem download the tool ‘IISCrypto” on your Exchange Server 2016 CU4. Both Exchange installations, on Windows Server 2012 R2 and Windows Server 2016, could be fixed with that tool by NARTAC SOFTWARE.
Download IISCrypto

Afterwards run the downloaded ‘IISCrypto.exe*’ file on your Exchage Server 2016. Maximize the appliacation window and choose thr button “Best Practices”. To start the changes press “Apply”.

IISCrypto

The programm will give you the hint to reboot the Exchage Server.

IISCrypto

After the reboot of the related Exchange Server, Outlook on the web (OWA) will be reachable by any supported browser vendor.

Le mail rimangono bloccate nella cartella bozze in Exchange 2010/2013

fonte:http://www.mazzolagiorgio.com/index.php/knowledge-base/23-le-mail-rimangono-bloccate-nella-cartella-bozze-in-exchange-2010-2013

Potrebbe capitare nell’uso di Exchange 2010/2013 che i messaggi di posta elettronica rimangano bloccati nella cartella bozze della cassetta postale mentre in osta inviata non ve n’è traccia.

Quando l’utente manda il comando di invio della mail lo “store driver” la processa e la gira al servizio di trasporto ma se questo processo non avviene (il servizio non è disponibile oppure non è in grado di processare la posta in uscita) la mail rimane nelle bozze.

 

L’inconveniente potrebbe essere dato da una non corretta configurazione nei DNS quindi basta collegarsi alla Exchange Admin Center, selezionare “server” sulla sinistra e modificare il server in oggetto. Nella voce “Ricerche DNS” selezionare “impostazioni personalizzate” e compilate sia la sezione “ricerche nel dns esterno” sia “ricerche nel dns interno”. Riavviate il servizio di trasporto di exchange e vedrete la posta inviata senza problemi.

Windows Server 2016 Download Maps Manager Delayed Start

fonte:https://www.interactivewebs.com/blog/index.php/server-tips/windows-server-2016-download-maps-manager-delayed-start/

Windows Server 2016 Download Maps Manager Delayed Start Red in Server Manager Dashboard

Its kind of annoying to find that after a fresh install of Windows 2016 Server you have a service that fails to behave correctly.

Download Maps Manager Delayed Start

When you click on the service, you will see something like this.

Screenshot 2017 08 02 22 40 27

Even if you attempt to force a start, it does not resolve this issue.

The good news is that this service is really not something you want anyway if you have a windows server doing actual server functions.

The Fix

The simple fix is to disable this service. The easy way to do this is to:

Open Windows Powershell

Windows 2016 Server Power Shell

Windows Powershell

Type this command:

Get-Service -Name MapsBroker | Set-Service -StartupType Disabled -Confirm:$false

Enter

Disable MapsBroker in Powershell

Problem is now fixed, and this annoying service is off and will not bother you again.

SQL Server – Recuperare il Product Key da una installazione esistente

fonte: http://www.ryadel.com/sql-server-2008-2008-r2-e-2014-recuperare-il-product-key-da-una-installazione-esistente/

A volte può essere necessario recuperare il Product Key del proprio SQL Server da una installazione esistente: il caso più comune è quello di un Server di una certa età del quale si è perso ogni ricordo di configurazione e che si ha improvvisamente necessità di trasferire altrove, ma può anche capitare di smarrire semplicemente il codice seriale e trovarsi nell’esigenza di doverlo recuperare.

Fortunatamente, l’informazione può essere agevolmente ottenuta tramite l’esecuzioe di questo script PowerShell realizzato da Jacob Bindslet:

Lo script funziona con tutte le versioni e le edizioni di SQL Server dalla 2005 in poi: SQL Server 2005, SQL Server 2008 e SQL Server 2008 R2: per utilizzarlo con Sql Server 2012 o Sql Server 2014 dovrete apportare delle piccole modifiche.

Nel caso di Sql Server 2012 dovete modificare la linea 5 nel seguente modo:

E anche modificare la linea 16 nel seguente modo (grazie a gprkns per il suggerimento):

Una versione completa dello script modificato in questo modo per funzionare su Sql Server 2012 è disponibile a questo indirizzo.

Nel caso di Sql Server 2014, Microsoft ha spostato il nodo DigitalProductID  all’interno della chiave di registro relativa all’istanza dell’installazione di Sql Server: per questo motivo dovrete modificare la linea 5 nel modo seguente:

Per eseguire lo script è sufficiente compiere queste operazioni:

  • Lanciate un prompt PowerShell (Avvio > Esegui (oppure Start > Run se il sistema è in lingua inglese), quindi digitate powershell e premete invio.
  • Copiate il testo della funzione di cui sopra e incollatelo direttamente all’interno del prompt.
  • Premete INVIO una o più volte, fino a quando il prompt non tornerà disponibile.
  • scrivete GetSqlServerProductKey e premete INVIO.

Se tutto è stato eseguito correttamente il Prompt si riempirà di una serie di informazioni nel seguente modo:

sql-server-2008-retrieve-product-key

Potrete così visualizzare la versione di SQL Server installata, l’architettura, la build, l’edizione e, soprattutto, il vostro Product Key.

Per il momento è tutto: felice recupero!

P2V – anolamie e soluzioni

https://blog.workinghardinit.work/2016/09/08/disk2vhd-on-a-generation-2-vm-results-in-an-unbootable-vhdx/

Disk2VHD on a Generation 2 VM results in an unbootable VHDX

Most people who have been in IT for a while will know the Windows  Sysinternals tools and most certainly the small but brilliant Disk2VHD tool we can use for Physical To Virtual (P2V) and Virtual to Virtual (V2V) conversions. It’s free, it’s good and it’s trustworthy as it’s made available by Microsoft.

For legacy systems, whether they are physical  with IDE/SATA/SAS controllers or virtual with an IDE generation 1 VMS thing normally go smooth.

image

But sometimes you have hiccups. One of those is when you do a V2V of a generation 2 virtual machine using Disk2VHD. It’s a small issue, when you create a new generation 2 VM and point it to the OS vhdx it just won’t boot. That’s pretty annoying.

image

Why do a V2V in such a case you might ask. Well, sometimes is the only or fasted way to get out of pickle with a ton of phantom, non-removable checkpoints you’ve gotten yourself into.

But back to the real subject, how to fix this. What we need to do is repair the boot partition. Well recreate it actually as when you look at it after the conversion you’ll notice is RAW. That’s no good. So let’s walk through how to fix a vdhx that your created from a source generation 2 Hyper-V vm via Disk2VHD.

First of all create a new generation 2 VM that we’ll use with our new VHDX we created using Disk2VHD. Don’t create a new vdhx but select to use an existing one and point it to the one we just created with Disk2VHD. Rename it if needed to something more suitable.

Don’t boot the VM but add a DVD and attach the Windows Server ISO of the version your vhdx contains to the DVD.

image

Move the DVD to the top of the boot order I firmware.

image

The VM will boot to the DVD when you hit a key.

Select your language and keyboard layoout when asked and the don’t install or upgrade the OS but boot

image

image

 

image

 

 

image

 

image

Type diskpart and  list the disks. Select the disk we need (the OS disk, the only one here) and list the volumes. You can see that volume 3 off 99MB is RAW. That’s not supposed to be that way. So let’s fix this by creating boot loader directory structure, repair the boot record by creating the boot sector & copy the needed boot files into it.

Type:

select volume 3

assign drive letter L:

FORMAT FS=FAT32 LABEL=”BOOT”

That’s it we can now us that 99MB volume to make our disk bootable to windows again.  Type Exit to leave diskpart.

image

So now we have a formatted boot partition we can create the need folder structure and fix the boot record and configure our UEFI bootloader

Switch to the L: volume

create efi\microsoft\boot folder structure for the bootloader as show below with the md command(make directory)

Type: bootrec /fixboot to create the bootrecord

Type: bcdboot C:\Windows  /l en-us /s l: /f ALL

This creates the BCD store & copies the boot files from the windows system directory

You can create all the directories in one go by doing
mkdir -p L:/efi/microsoft/boot/

 image

Just click Continue to exit and continue to Windows Server 2012R2

image

.. and voila, your new VM has now booted.

image

Now it’s a matter of cleaning up the remnants of the original VMs hardware such as the NIC and maybe some other devices. The NIC is very important as it will have any static TCP/IP configuration you might want to assign tied to it which mean you can’t reuse it for your new VM. So, the 1st thing to do is uninstall the old network adapters from device managers, you’ll see them when you select “show hidden devices” in the view menu.

Good luck!

How to manually purge Exchange server logs – clean and easy

https://ilantz.wordpress.com/2011/10/26/how-to-manually-purge-exchange-server-logs-clean-and-easy/

This example will show you how to purge the logs for a database that is located on Drive D. we will “fake backup” drive D and this will trigger the logs to be purged.

  1. Open Command prompt
  2. Launch Diskshadow
    1. Add volume d:
    2. Begin Backup
    3. Create
    4. End Backup
  3. At this step you should notice the following events in the application log indicating that the backup was indeed successful and logs will now be deleted.

Here’s some screenshots from the process:

Diskshadow commands for the example

How to grant insert in a table that is in another database on SQL Server 2008 R2?

fonte: https://dba.stackexchange.com/questions/96629/how-to-grant-insert-in-a-table-that-is-in-another-database-on-sql-server-2008-r2

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4c12914c-8364-48f4-ad35-db64fbeb0ff1/how-to-give-read-write-permissions-to-a-specific-table-in-a-database-of-sql-2008r2?forum=sqlgetstarted

Use [DatabaseA]
GO

ALTER DATABASE [DatabaseA]
SET DB_CHAINING ON
GO

Use [DatabaseB]
GO
ALTER DATABASE [DatabaseB]
SET DB_CHAINING ON
GO

EXEC sp_grantdbaccess 'UserB';
GO 

GRANT SELECT, UPDATE on [DatabaseB].[dbo].[TableA] TO [UserB]
GO