Recently we had jobs for a server showing up the error : NFC storage connection is unavailable

Image result for NFC storage connection is unavailable

Turns out a colleague had added a server to the Veeam application with a tape drive to the unit which had actually added that server as a Veeam Backup Proxy!

Jobs actually default to “Use Any Available Proxy” so the Jobs were using the tape drive server as a proxy for some of the Jobs hence the NFC Failure

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

 

 

Recently we swapped a users UPN on a local domain controller ( which syncs to 365 via AAdconnect) to another domain and SMTP alias, all worked well however she could not login to Skype for Business.

Resetting Windows Credentials, Caches and registry items still would not fix this.

Most of the time this is due to the SIP Address not being correct. Little did we know this user had Lync before migrating to 365 so they had a SIP address in the attribute editor

Changing this resolved the issue

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

If you are trying to get the size of your Synology Volume via SNMP < you will need to query the correct Index on the OID .1.3.6.1.2.1.25.2.3.1.3.

Synology does not have standard indexes , so you will need to start by downloading run and install SNMP walk on a machine that can communicate to the device over network

Enter the IP of the device in SNMP Walk ( Leave rest options to default ) and get the output to text File

Open the txt file and do a Search for volume and per below you should fine the list of OID’s

The last number will be the index , for example Index will be 41 fo the volume

.1.3.6.1.2.1.25.2.3.1.3.1 = STRING: “Physical memory”
.1.3.6.1.2.1.25.2.3.1.3.3 = STRING: “Virtual memory”
.1.3.6.1.2.1.25.2.3.1.3.6 = STRING: “Memory buffers”
.1.3.6.1.2.1.25.2.3.1.3.7 = STRING: “Cached memory”
.1.3.6.1.2.1.25.2.3.1.3.8 = STRING: “Shared memory”
.1.3.6.1.2.1.25.2.3.1.3.10 = STRING: “Swap space”
.1.3.6.1.2.1.25.2.3.1.3.31 = STRING: “/”
.1.3.6.1.2.1.25.2.3.1.3.36 = STRING: “/tmp”
.1.3.6.1.2.1.25.2.3.1.3.37 = STRING: “/run”
.1.3.6.1.2.1.25.2.3.1.3.38 = STRING: “/dev/shm”
.1.3.6.1.2.1.25.2.3.1.3.41 = STRING: “/volume1”

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently , users where getting the below error from a Web App they use

This is due to the mixed code security which needs to be set to : “Enable – hide warning and run with protections”

To deploy this setting to all computers on a network via Group Policy follow the guide below , here is the Java Reference

Create a GP to delpoy the following file to C:\Windows\Sun\Java\Deployment\deployment.config

deployment.system.config.mandatory=true
deployment.system.config=file:///C:/WINDOWS/Sun/Java/Deployment/deployment.properties

Create a GP to delpoy the following file to C:\Windows\Sun\Java\Deployment\deployment.properties

# Mixed code (sandbox vs. trusted) security verification
deployment.security.mixcode=HIDE_RUN
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently had a few Zerto Recovery Groups ( VPG’s ) came up with the state 

Recovery is possible. (0%)

Connecivity to the VM’s where ok , and when I ran through the Wizard after Editing the VPG is came back with all ticks. A reboot of the server and SCVMM server did not clear the issue either

In the end we had to perform a “Force Sync” to resync the delta’s

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Recently I was trying to get a WDS server PXE Booting using Legacy and UEFI booting. I followed the DHCP guide here Legacy worked however UEFI was not working. I double checked on the WDS server for the 67 Option with a file share and in

\\%IPOFSERVER%\reminst\Boot\x64

wdsnbp.com existed but no wdsmgfw.efi

Running a rebuild of the boot files also did not fix this for some reason , in the end I copied the file from : 

\\%IPOFSERVER%\c$\Windows\System32\RemInst\boot\x64

and it resolved the issue

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

How to get the OneDrive .ADMX files for Group Policies

On a machine with the latest of One Drive for Business installed, navigate to : %localappdata%\Microsoft\OneDrive

Find the latest version number in the folder and open it then go to the adm folder and copy the  .admx file

to \\domain.local\SYSVOL\domain.local\Policies\PolicyDefinitions and .adml file to \\domain.local\SYSVOL\domain.local\Policies\PolicyDefinitions\en-us\

Set Policies

Configure your Group Policies to the settings you want, but the one you’ll need for auto sign in is “Silently configure OneDrive using Windows 10 or domain credentials“. ) This will set : [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive] “SilentAccountConfig”=dword:00000001. 

and also it will set Modern Authentication: 

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\OneDrive] “EnableADAL”=dword:00000001 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

So you’ve found an issue in a Package in a Project for a DataSynchronization in a Integration Services Catalogs ( .dtsx file ) that you want to edit?

Install if its not already on it and open SQL Server Data Tools

Click on File and New Project

Choose this Project

Choose “Intergration Servies Catalog” and Open the project

You should see the .dstx files on the right under

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

You will probably be given the files in a Zip file something like

SV9100_UC_Suite_AU_v4.5.4_R2

Extract this zip file

Download and install 7zip then extract UC_InConnect-4_5_4.exe to a folder UC_InConnect-4_5_4

You will now see the MSI file to install 

UcConnector.msi

Move this file to a share on a server ( or DFS location if you have multiple sites ) and make sure Domain Computers has read Access to the Share and the security on the folder

Create a new Group Policy and add it to the Policy Assigned Apps

How apply this policy to the Workstations OU

And on reboot you should see the below on the desktop

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)