Network Audit and Documentation, CENTREL Solutions Blog

We now have a review of XIA Configuration Server live on the 4SYSOPs web site https://4sysops.com/archives/xia-configuration-easy-network-inventory-and-documentation-solution/ 4sysops is an online community for IT professionals. Experienced IT pros cover the latest technologies in system administration, cloud computing and DevOps.

We've recently stumbled upon a problem with reading registry entries using PowerShell where the Get-ItemProperty or Get-Item cmdlet returns garbled registry values with artifacts. You'll notice that Regedit shows ellipses ("...") after the registry value. For example here's the ODBC settings for the Oracle ODBC driver. If you double click the registry value however it shows correctly. When you try get the value using PowerShell things get very messy Get-ItemProperty -LiteralPath "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\ODB C\ODBCINST.INI\Oracle in client" -Name Driver If you read the registry value using WMI using the standard WMI registry provider , this shows the string correctly. What is happening here is that the string in the registry is stored as a null-terminated string, and after the null terminator a lot of binary data has been dumped that we're not meant to see. Obviously this data should really be stored in another REG_

You may find when using the PropertyGrid in a C#.NET Winforms application that the PropertyGrid displays an alert with the title "Properties Window" and the message "Index was outside the bounds of the array" when you are editing a collection. This is a somewhat misleading error as this can occur if you are modifying a Collection<T> where the object /// <summary> /// Represents an ODBC data source property. /// </summary> [ Serializable ] [ XmlRoot ( "Property" )] public abstract class OdbcDataSourceProperty : GlobalSerializableBase , IComparable < OdbcDataSourceProperty > { Remove the abstract modifier and the problem will go away.

It seems there is a bug in Windows 10 that if you change the WINS primary or secondary IP addresses in the user interface these are not updated immediately in the Win32_NetworkAdapterConfiguration WMI class. The following shows no WINS servers Get-CimInstance Win32_NetworkAdapterConfiguration|SELECT Description, WINSPrimaryServer However disabling and re-enabling the network adapter seems to resolve the issue.

The program can’t start because MSVCR120.dll is missing from your computer. Try reinstalling the program to fix the problem. If you see this problem you need the Visual C++ Redistributable Packages for Visual Studio 2013  This can be downloaded here https://www.microsoft.com/en-gb/download/details.aspx?id=40784 This should resolve the issue.