SSH Keys – Access SSH without password – Windows/Linux

Prerequisites:

  • Make sure guest machine has ssh installed.
  • Make sure the SSH key is created in the proper ../.ssh directory, or the install of the SSH key will fail (due to permissions).

Everything is done on the host machine. For this example, I am using a Windows machine with GitBash:

Diskwipe – data removal / destruction – tmp files in $diskwipe directory

Ran through Diskwipe with the erasing pattern Russian GOST P50739-95 – (2 passes – quick). After the wipe had completed, I ran EaseUS data recovery to see what it could detect, and it had detected tmp files in the $diskwipe directory (titled tmp0001, tmp0002, etc)

I formatted the disk manually from Windows and started the wipe again to see how it would respond.

While the program was running through “secure erasing disk” on the second wipe, I opened the drive I was wiping, and could actually see the bits being written in 2GB files in live time. This is because the software is writing files to the disk:


It was unclear of what the tmp files were, but after seeing this, makes much more sense. Hope this helps someone out with the same question as me!

You can get the tool here: http://www.diskwipe.org/

Office 365 – Enable In-Place Archiving – Warning: The user hasn’t logged on to mailbox ‘name’.

Attempted to enable Archiving for one mailbox in O365 Exchange Center, but I kept receiving a Warning message when going into ‘View Details’ after enabling the account.

I needed to query the last logon time for the mailboxes to confirm there was a last logon:

Then, I needed to enable the mailbox with PowerShell.

In order to start emails syncing to the Archive mailbox, it can take up to 24 hours to initialize. We need to run an additional command to get the mailboxes syncing:

Veeam – Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [238]. Failed to download disk.

Did quite a bit of research on this. Updated network settings, searching through numerous Log files, Event Viewer, registry settings, running DISM and sfc commands, installing a completely separate Veeam Backup server; you get the idea.

The solution to my problems was to run the backup job locally (Veeam Workstation) to get additional information.

As you can see, it is first erroring out at \\?\Volume…(disk 6).

I opened diskmgmt.msc . I have a dual boot system with Windows 7 I use occasionally for offline music production (because of compatibility issues). The disk 6, 2.4 GB was a System Recovery Drive for the Windows 7 OS, let’s call this drive J:\ . Keep in mind that I am only attempting to back up my live Windows 10 OS’s C:\ drive (specifically C:\ drive, and not the option “Operating System”). Somehow Veeam was attempting to backup the J:\ System Recovery Drive and erroring out because of it.

I deleted the System Restore partition with diskpart and ran the backup job locally with the Veeam Workstation client. Success! Backup ran without issue! I reverted my changes in Veeam to use the backup server instead, and the backup there was also successful. Since I was able to backup the C:\ drive successfully, lastly I chose the “Operating System” option, and again was successful.

Microsoft Deployment Toolkit (MDT) MMC Error – Windows PE

When setting up MDT with ADK, I installed both MicrosoftDeploymentToolkit.msi and adksetup.exe . Everything appears to be working normally, but when I go into the “DeploymentShare” -> “Properties” -> “Windows PE”, I receive an MMC snap-in error:

To resolve this issue, I looked at the error:

I did some research and I discovered that we also need to install Windows PE, which does not seem to come with ADK (as I recall, WinPE used to come with the default ADK install). In order to install Windows PE, I followed this link: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/download-winpe–windows-pe

After installing WinPE, I no longer received the MMC error.

Office 365 Applications won’t install. Stuck at “Getting things ready”.

Sometimes Office fails to install. Usually will state “Getting things ready” indefinitely:

Microsoft came out with a tool, SARA (Microsoft Support and Recovery Assistant). https://diagnostics.office.com

Download and run the tool. Proceed through the prompts as necessary. This will resolve any issues with the install, or at minimal, give you an explanation on why the install is not working.

In this case, Microsoft Office 2010 64-bit was installed and needs to be removed to proceed with the O365 install.

PowerShell – O365 – Force Mobile Device Quarantine to ‘Allow’ Device with PowerShell.

O365 – Force Mobile Device Quarantine to Allow Device with PowerShell. Devices get stuck in Exchange portal where you can’t allow or deny them.

Ocassionally, when allowing all devices in the Exchange portal of Office365, some items seem to get stuck in Quarantine. When selecting ‘Allow’ or ‘Deny’, the request times out and switched back to ‘Quarantined’.

We can force this change through PowerShell. Make sure that the IDENTITY is unique (one of a kind) or there will be issues:

After this was run for each user/device stuck in quarantine, they were all set to ‘Allow’ the device.

Email on ping failure, Email again on ping success; Loops indefinitely; encrypted password

I was experiencing issues at a remote location. I needed to know how frequent this location was losing Internet (router), as staff had reported this being an issue here and there. We had switched from DSL to Cable, and we wanted to know if this resolved all of the problems. I was able to search my gmail through the timestamp and show that we were up and running at 99.999% uptime.

Ran the script once, and encrypted password was used as authentication. Still fairly a beginner in PowerShell, but this may be of help to someone. If anyone has suggestions, I am interested in hearing them out.

The only two lines *in* the script that need to be edited is ($IPAddress) and ($LocationTitle) . Of course I could have made these a Read-Host. Edit: Also the To, From, CC section; didn’t need to change once set personally.

#Reference: https://stackoverflow.com/questions/12460950/how-to-pass-credentials-to-the-send-mailmessage-command-for-sending-emails

Powershell – Query and uninstall WebEx. Vulnerability (2018-04)

The following will search for and uninstall WebEx. If the uninstall fails, it will state that we need to remove/update manually:

The following will only search if WebEx is installed: