13 dic 2017

RITORNA IL SID ROADSHOW: L'EVENTO A CASA TUA!


Sarò presente a Mestre e parleremo di migrazione di Exchange Server verso Exchange Online.



RITORNA IL SID ROADSHOW: L'EVENTO A CASA TUA!
Anche nel 2018 ci sarà il SID Roadshow, l'evento itinerante, in tre tappe, che porta a casa tua l'esperienza della conferenza IT Pro for Business più importante d'Italia.
GDPR, security, virtualizzazione, cloud, storage, management, container e molto altro. Ecco alcuni degli argomenti che tratteremo durante le varie tappe, che per la prima volta non avranno la stessa agenda. I temi proposti verteranno sulle ultime tecnologie, come Windows Server v1709, Windows 10, Microsoft Azure, Microsoft Office365, Microsoft Intune e molto altro ancora. Non mancheranno le sessioni dei nostri sponsor, e partner, che vi proporanno le loro soluzioni per migliorare il vostro reparto IT, ottimizzare i costi e migliorare la produttività.
SAVE THE DATE!
Ti aspettiamo il 25 gennaio a Reggio Emilia (in collaborazione con Progel), il 30 gennaio a Torino (in collaborazione con ACME Consulting) ed il 1 febbraio a Mestre (in collaborazione con Walk2Talk).
I posti sono limitati, quindi non perdere tempo ad iscriverti! Ma ricordati di farlo solo se sei realmente certo di poter essere dei nostri.
STAY TUNED!
Seguici tramite i nostri canali social per rimanere sempre aggiornato sulle ultime novità della conferenza ed usa l'hashtag #sidrs18 per vivere assieme noi l'attesa del SID Roadshow 2018.
Se pensi che questa occasione sia importante anche per qualcuno che conosci, sentiti libero di invitarlo ad iscriversi subito alla conferenza. Ricorda che i posti sono limitati.
     

7 dic 2017

Windows DC: ERROR 0XC00002E2 in the virtualized environment

#Note
If you are using windows server as a virtualized domain controller and you can see this error:  0XC00002E2 during the boot phase and after a restore.

#Product Affected
Windows 2012 DC and probably also other versions

#Solution
- Restart the instance and press F8 until the boot menu appear
- Boot into Directory Services Repair Mode (DSRM)
- Login with a local administrator account, since AD service will not be running so the domain user will not be available.
- Backup everything in C:\Windows\NTDS
- Open a Command Prompt (Win-R, CMD, Enter)
- Type NTDSUTIL and press Enter.
- Type "activate instance ntds" and press Enter. Type “Files” and press Enter.
- Type “Info” and press Enter (this will shows you the logs location in case if you have more than one partition).
- Navigate to logs Location and delete (or rename) the *.log.
- Reboot
- Boot into Directory Services Repair Mode for second time
** Now have to defrag the database, while in DSRM;
- Open a Command Prompt (Win-R, CMD, Enter). Type NTDSUTIL and press Enter.
- Type “activate instance ntds” and press Enter.
- Type “Files” and press Enter.
- Type “Info” and press Enter. Verify the folder is actually C:\Windows\NTDS.-
- Type “Compact to ” and press Enter. I created C:\Windows\NTDS\Temp and used that.
- Copy the new file Ntds.dit in the temp folder over the old one in NTDS, and delete all the *.log files.
- Reboot normally.

26 nov 2017

MBR2GPT: ValidateLayout: Too many MBR partitions found, no room to create EFI system partition.

#Note
When you try to convert Windows 10 to UEFI, so partition from MBR to GPT, MBR2GTP fail.
The command return this error:

Info           ESP partition size will be 104857600
Info           MBR2GPT: Validating layout, disk sector size is: 512 bytes
Error         Validate Layout: Too many MBR partitions found, no room to create EFI system partition.
Error         Disk layout validation failed for disk 0
Info           MBR2GPT: Partition information at error point

#Product affected 
Windows 10 1703 and above

 #Solution 
The mbr2gpt disk conversion tool need three conditions for the validation of disk layout:
- Admin rights
- One of physical disk with boot partition MSR and OS partition
- The validation allows normally one of additional partitions, often it's recovery partition
If you have more than three partition validate will fail.

Check this with Get-Partition cmdlet










In this case we have too partition, so we have to find the Windows Recovery Environment (Windows RE)  partition with the command ReAgentc /info


Now we have to remove the "exceed" partition (partition 4)



And finally we can convert BIOS to UEFI with:

mbr2gpt /convert /disk:0 /allowfullos

















21 nov 2017

Poweroff Linux based NAS (Synology, ecc) remotely from Windows by command line

#Note
I had to turn off the NAS automatically after a Veeam backup copy process, but... it's not as simple as I thought.
The problem is that Linux SSH security permit executing of the "power off" command only as root and then root can not login to SSH

how do to do?

#Product affected / related 
NAS Linux based, Linux and Windows Server and Clients

#Solution 
1. Login to your NAS as admin user by SSH (PuTTY)
To enable ssh on Synology:
Control Panel > Terminal & SNMP > Terminal allows your Synology NAS to support Telnet and SSH command-line interface services. You can also change the security level of the SSH encryption algorithm.
To enable Telnet/SSH service:
Check the box next to the SSH protocol
Click Apply

2. Take permission as root
sudo su - or sudo -i

3.  Edit /etc/group
vi /etc/group

add a line for group shutdown and add your user name to it

poweroff:x:510:yourUserName

4. Change permissions to allow the shutdown group read and execute permission.
chmod 750 /sbin/poweroff

5. Power off can only be run by root so you need to have group "poweroff" execute the program as if you were root.
chmod u+s /sbin/poweroff

Now we have the "permission" to power off the system as admin 

6. Download plink
On Windows, you have to download plink from PuTTY download page and save it in a folder.
This is the command that resolve the problem:

plink.exe -ssh -t -pw “yourpassword” admin@xxx.xxx.xxx.xxx "poweroff"










20 nov 2017

Epson LQ can't print on Windows 7 /10 after recent patch


#Note
Epson LQ printers are not able to print after the installation of recent patch KB2952664 and KB4048957 on Windows 7 and KB4048955 (Windows10 Version 1709), KB4048954 (Windows 10 Version 1703), KB4048953 (Windows 10 Version 1607), KB4048952 (Windows 10 Version 1511), KB4048956 (Windows 10 Version 1507)

#Product affected / Related
Windows 7 32 and 64 bit, Windows 10

#Solution 
Remove the KB2952664 and KB4048957 on Windows 7 or the KB4048955 (Windows10 Version 1709), KB4048954 (Windows 10 Version 1703), KB4048953 (Windows 10 Version 1607), KB4048952 (Windows 10 Version 1511), KB4048956 (Windows 10 Version 1507)

Use PowerShell Cmdlet Get-Hotfix to verify the presence of the patches

To unistall KB:
wusa /uninstall /Kb:XXXXX

Pay Attention:
Patches are reinstalled if they do not hide from Windows Update