Post in evidenza

Recovery - Access, Excel, Word, Office and Photo recovery tools and other blog procedures

During these years I had necessity to recover various files (.doc, mdb, .xls, photos...)  I utilized various free tools (here is an exampl...

WSUS - Reinstall WSUS with clean Settings

You can go here:

cd %drive%\Program Files\Update Services\Tools

wsusutil reset

To re-install WSUS with a clean database ie no previous configuration;

Run Windows Powershell as Administrator and use the following commands:

Uninstall-WindowsFeature -Name UpdateServices,Windows-Internal-Database -Restart

Post restart, delete EVERYTHING in the "C:\Windows\WID" (for Win 2012 r2) folder, then run the following command to re-install WSUS:

Install-WindowsFeature UpdateServices -Restart

This only works on Powershell 3 or higher. More info here: https://technet.microsoft.com/en-us/library/cc732257.aspx

==============================================================

Related articles:


Backup - Veeam endpoint Backup unattended upgrade installation procedure

As discussed in precedent post veeam endpoint backup is a free tool to backup pc and, in case, is able to backup on Veeam B&R repository to have double backup location and backup policies.

Veeam - Veeam Endpoint free and centralized console Veeam Endpoint Backup for LabTech

Veeam - Veeam Endpoint Backup Free - Free version released

At the same time, if you uncheck veeam backup autoupdate, there is an interesting aspect about silent installation mode parameters.



you can later push that centrally with other tools like:

- PSEXEC
- SCCM
- PDQ

a.) Installation Syntax

To install Veeam Endpoint Backup in the unattended mode, use a command with the following syntax:

/silent

where is a path to the Veeam Endpoint Backup installation file.


You can upgrade Veeam Endpoint Backup to a newer version in the unattended mode using the same command that is used for unattended installation. To learn more, see Installing Veeam Endpoint Backup in Unattended Mode.

c.) Using Sysprep and Veeam Endpoint Backup


You can pre-install Veeam Endpoint Backup in a custom Microsoft Windows system image that will be used for deployment on different computers. To do this, you should perform a set of configuration steps in the reference Microsoft Windows system installation that will be included in a deployment image.
To configure a custom Microsoft Windows system image with Veeam Endpoint Backup:
  1. Install Veeam Endpoint Backup in a Microsoft Windows system image. To learn more, see Installing Veeam Endpoint Backup.
  2. Configure the backup job in the way you want it to work on computers with pre-installed Veeam Endpoint Backup. To learn more, see Configuring Scheduled Backup Job.

Using Sysprep and Veeam Endpoint Backup Note:
It is advised to configure the backup job for the entire computer backup. In case of volume-level backup, it may be necessary to reconfigure the backup job after Microsoft Windows is deployed to the target computer and include the necessary volumes in the backup once again. This may happen if volumes' GUIDs were changed at the stage of Microsoft Windows generalization with Sysprep.

  1. Create a registry key value: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\SysprepMode (DWORD)=1.
This registry key value is used to regenerate the job ID when Veeam Endpoint Backup starts for the first time on the new computer. If you do not create the registry key value, the backup job may fail as soon as it is started on the new computer.
  1. Run the Sysprep tool in the Generalize mode to remove any system-specific data. If you need to run the Sysprep tool in the Audit mode, do not forget to re-create the registry key afterwards.
  2. Deploy the image on the necessary computers in any convenient way. To learn more about deployment of Microsoft Windows system to new computers, see https://technet.microsoft.com/en-us/library/dd349343.aspx.

Network - FortiMail Antispam and ingoing and outgoing message size modify

If you are using Fortimail VM as antispam system you could have necessity to change SMTP ingoing and outgoing email.

You need to go to profile --> Session --> for each profile --> SMTP Limits --> Cap message Size (KB) at.


Take in consideration this fortinet manual advice.







Backup - ShadowCopyView tool that lists snpashots

ShadowCopyView is new tool for Windows 10/8/7/Vista that lists the snapshots of your hard drive created by the 'Volume Shadow Copy' service of Windows. Every snapshot contains an older versions of your files and folders from the date that the snapshot was created, you can browse the older version of your files and folders, and optionally copy them into a folder on your disk.

You can download it from here:

http://www.nirsoft.net/utils/shadow_copy_view.html

Exchange 20xx - Windows backup usage to backup store

You can use Windows Server Backup to backup Exchange store.

Is not excellent but it can be useful as first backup step.

1. Go to powershell:

PS C:\> Import-Module servermanager
PS C:\> Add-WindowsFeature backup

2. Select Exchange store and partition log

2. Select the VSS Settings tab and make sure that VSS full backup is chosen.  Click OK

Here they are more precise articles to go deeper on this argument:

http://www.techrepublic.com/blog/the-enterprise-cloud/back-up-exchange-2010-with-this-windows-server-2008-r2-feature/

http://exchangeserverpro.com/exchange-2010-mailbox-database-backup-restore-windows-server-backup/

Backup - Robocopy and real time monitoring of any file changes

During these years we found possibility to launch robocopy that, in real time, monitor folder files and copy immediately to destination if any changes occurs.

Here you can reviews various blog's articles related to robocopy command.

Scritping - Using robocopy to replicate files to remote location on scheduled tasks and sending final log and status email

http://www.alessandromazzanti.com/2014/01/scritping-use-robocopy-to-replicate.html

Backup – Lista dei comandi di Robocopy

http://www.alessandromazzanti.com/2013/02/backup-lista-dei-comandi-di-robocopy.html

Tips - How to migrate file server share and permissions

http://www.alessandromazzanti.com/2015/11/tips-how-to-migrate-file-server-share.html

Here is parameter syntax about real time backup.

/MON:n :: MONitor source; run again when more than n changes seen.
/MOT:m :: MOnitor source; run again in m minutes Time, if changed.

Here is a sample .cmd string line:


start /b robocopy %USERPROFILE%\Desktop \\SERVERNAME\BackupUsers$\%computername%\%username%\Desktop /mon:1 /E /ipg:25 /w:10 /r:1 /XF "*.pst" /log:\\ SERVERNAME \BackupUsers$\%computername%\%username%\Logs\%mydate%_Incremental_Robocopy_Desktop.log /NP

Veeam One - Several alerts Host disk SCSI aborts

If you get several alerts about ISCSI aborts, here is a sample message:

Alarm: Host disk SCSI aborts
Time: xx/xx/201x xx:xx:xx
Details: "Disk/ESXi: Datastore Command Aborts" (5.0 Number) is above a defined threshold (2.0 Number) for 'DatastoreXXXXXXX';

KB article

Summary: This host disk (vmhba) has logged one or more SCSI aborts

Cause: This monitor is configured to alert on any SCSI Aborts. The host systems use the SCSI protocol to communicate to disks, even over Fiber Channel to SAN LUNs. SCSI Bus Aborts are in effect the SCSI subsystem timing out and commands being canceled. This happens when the HBA device is overloaded, or its q-depth is exhausted. The first thing to know is which vmhba controller (C), target/path (T), and LUN (L) experienced these problems. The more VMs sharing a single LUN the more likely that resets will occur. Rule of thumb is no more than 10 VMs sharing a LUN, although performance of storage subsystems and VM workload demands mean this number may vary

Resolution: Check the status of the disk subsystem and connectivity. Check for possible disk hardware, firmware or driver issues. See historical graph of SCSI aborts

External: Refer to VMware's online documentation for more information


In that case, there are two things you can do. Edit the alarm so that it only fires up when you need it should, as default values are very strict, and second, refer to VMware online documentation for additional information on the SCSI aborts themself - this is not the Veeam ONE part).

The link is found in the Knowledge Base in the alarm itself.

Editing alarms is done from Veeam - Alarm Management - find the alarm - "edit" and there you can change the Rules so that the alarm appears less often, or even suppress it for certain time periods (other options, like suppress during backup, are currently experimental and work only on backup itself) and there is also the KB with links as said before.

Then I went deep on this kind of alarm and so I logged on vSphere client following this interesting article:

https://lazyadminblog.com/2015/05/09/how-to-monitor-the-disk-command-aborts-on-an-esxi-host/.

On vSphere client -->Performance-> Advanced -> Switch to disk -> chart options...-> commands aborted-> ok.



In precedent article is verbosely explained how to monitor that value through putty too/command line.

720check