I recently had an issue with an internal website with no certificate. When trying to access the site via IE10 I was not being given an option to "Continue to this website". This was due to a change Microsoft made blocking the use of RSA certificates with keys less than 1024 bits long.
Microsoft's Security Advisory bulletin can be found here: https://support.microsoft.com/en-us/kb/2661254
To fix this, run CMD as administrator and submit the following command;
certutil -setreg chain\MinRSAPubKeyBitLength 512
Then refresh the page. The "Continue to this website" option should be available again.
Labels
3300
(1)
3PAR
(1)
Active Directory
(1)
ADFS
(1)
Admin Share
(1)
Auto-Sync
(2)
Auto-Sync locked
(1)
AWS
(3)
AzCopy
(1)
Azure
(3)
Backups
(2)
Broadcom
(1)
Call Forwarding
(1)
CLI
(2)
cmd
(1)
Compatibility View
(1)
Dameware MRC
(1)
Databases
(1)
DFS
(1)
DNS
(1)
Domain Admin
(1)
domain controller
(1)
Enterprise Mode
(1)
ESXi 5.0
(1)
ESXi 5.1
(5)
ESXi 5.5
(3)
Exchange
(3)
Exchange 2010
(5)
Extreme
(1)
ExtremeXOS
(1)
Federation
(1)
File Share
(1)
FSMO
(1)
GPO
(1)
Group Policy
(1)
Group Policy Client
(1)
Hardware Acceleration
(1)
Helpdesk
(1)
HP-UX
(1)
Hyper-V
(2)
IAM
(1)
IE10
(1)
IE11
(1)
IP conflict
(1)
Kayako
(3)
LDAP
(1)
Licence
(1)
Links
(9)
local groups
(1)
LUN lock
(1)
LUN number
(1)
MAC address
(1)
Microsoft Teams
(1)
Mitel
(1)
Namespaces
(1)
Networking
(6)
Nexenta
(6)
NMC
(1)
Office 365
(4)
OneDrive
(1)
Outlook 2003
(1)
Outlook 2013
(1)
PC
(1)
Physical
(1)
PowerCLI
(10)
Powershell
(10)
promoted links
(2)
Public Folders
(1)
RDP
(1)
RDS
(1)
Recovery Services
(1)
RedShift
(1)
Registry
(3)
Reports
(1)
Resolve
(2)
Restart
(1)
RSA
(1)
Run As
(1)
SAML
(1)
SAN
(1)
Scavenging
(1)
script
(10)
Server 2003
(3)
Server 2008 R2
(1)
Server 2012 R2
(2)
Servers
(2)
sharepoint 2013
(3)
SMTP
(3)
Snapshot
(2)
SRM
(1)
SSH
(5)
SSL Certificate
(2)
Temporary profile
(1)
Terminal Server
(3)
Troubleshooting
(5)
Ubuntu
(1)
Update Manager
(1)
Useful Apps
(1)
VAAI
(1)
vCenter Server Appliance
(1)
VDI
(1)
VDP
(1)
Veeam Backup and Replication
(2)
VM
(1)
VM Error
(1)
vmdk
(1)
VMFS
(1)
vMotion
(2)
VMware
(20)
VoiP
(1)
vSphere 5.5
(4)
vSphere 6.0
(2)
vSphere 6.5
(1)
vUM
(1)
webpart
(1)
Windows
(3)
Windows 10
(1)
Windows 7
(2)
Friday, 18 December 2015
Wednesday, 16 December 2015
AWS RedShift Cluster Can Only Be Launched In Default VPC
When trying to launch a RedShift cluster in AWS I found I was only able to select the default VPC - unfortunately not the VPC that my Production workloads were running in.
In order to allow the creation of RedShift clusters in VPCs other than your default you need to create a new Cluster Subnet Group. To do this follow the steps below;
1. Login to AWS console and select RedShift
2. In the RedShift console go to "Security" and select "Subnet Groups" from the tabs at the top
3. Click "Create Cluster Subnet Group"
4. Give the group a name and description and pick the VPC you want to run the Cluster in. Then choose your Subnet IDs from the Availability Zones available.
5. Click "Create". Now when you try to launch a RedShift cluster you will be able to choose the VPC you want to run the Cluster in, and your newly created Subnet Group.
In order to allow the creation of RedShift clusters in VPCs other than your default you need to create a new Cluster Subnet Group. To do this follow the steps below;
1. Login to AWS console and select RedShift
2. In the RedShift console go to "Security" and select "Subnet Groups" from the tabs at the top
3. Click "Create Cluster Subnet Group"
4. Give the group a name and description and pick the VPC you want to run the Cluster in. Then choose your Subnet IDs from the Availability Zones available.
5. Click "Create". Now when you try to launch a RedShift cluster you will be able to choose the VPC you want to run the Cluster in, and your newly created Subnet Group.
Wednesday, 11 November 2015
Accessing Shares: "The account is not authorized to login from this station"
When trying to connect to an admin share (\\Servername\D$) I was seeing the error "The account is not authorized to login from this station"
This is due to an issue with SMB signing policies and can easily be fixed by ensuring the following keys have parameters as below;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
enablesecuritysignature = 1
requiresecuritysignature = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
enablesecuritysignature = 1
requiresecuritysignature = 0
In my case, I found that one of the lanmanworkstation keys did not match. After changing this I could access the admin share
This is due to an issue with SMB signing policies and can easily be fixed by ensuring the following keys have parameters as below;
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
enablesecuritysignature = 1
requiresecuritysignature = 0
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
enablesecuritysignature = 1
requiresecuritysignature = 0
In my case, I found that one of the lanmanworkstation keys did not match. After changing this I could access the admin share
Terminal Server Sessions Disabled
I ran into a couple of issues recently where I was no longer able to RDP onto a server. Whenever I tried to login I received an error "Terminal Server Sessions Disabled: Remote logins are currently disabled".
To fix this I opened up regedit, connected to the server in question by using the "Connect Network Registry" option (under "File" in regedit) and browsed to the following key;
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled
This was set to 1. I changed this to 0 and was able to login again.
To fix this I opened up regedit, connected to the server in question by using the "Connect Network Registry" option (under "File" in regedit) and browsed to the following key;
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\WinStationsDisabled
This was set to 1. I changed this to 0 and was able to login again.
Friday, 24 July 2015
Backup and Restore ESXi Host Configuration Data Using PowerCLI
To back up the configuration data for an ESXi host using the vSphere PowerCLI, run the command:
To restore the data to an ESXi Host the build number of the new host must match the build number of the host that created the backup file. Then;
1. Put the new host into maintenance mode;
Set-VMHost -VMHost "ip" -State "Maintenance"
2. Restore the configuration;
Set-VMHostFirmware -VMHost "ip" -Restore -SourcePath "location of file from backup operation" -HostUser "username" -HostPassword "password"
3. Exit maintenance mode;
Set-VMHost -VMHost "ip" -State "Connected"
Get-VMHostFirmware -VMHost "ESXi_host_IP" -BackupConfiguration -DestinationPath "location"
To restore the data to an ESXi Host the build number of the new host must match the build number of the host that created the backup file. Then;
1. Put the new host into maintenance mode;
Set-VMHost -VMHost "ip" -State "Maintenance"
2. Restore the configuration;
Set-VMHostFirmware -VMHost "ip" -Restore -SourcePath "location of file from backup operation" -HostUser "username" -HostPassword "password"
3. Exit maintenance mode;
Set-VMHost -VMHost "ip" -State "Connected"
Monday, 20 July 2015
Where are my FSMO roles?
The easy way to query which servers hold your FSMO roles is to open a command prompt and type;
NetDOM /query FSMO
This should return a list of each role and the server holding it.
NetDOM /query FSMO
This should return a list of each role and the server holding it.
Tuesday, 9 June 2015
PowerCLI - Generating A Network Configuration Report
I needed to generate a report from my vSphere environment to detail the network configurations of my various Hosts including the DataCenter and Cluster that the Hosts belong to, as well as vSwitch configs, any active and standby NICs that were assigned, port group name, VLAN ID, device type (ie vmk port) and any IP assigned. I also wanted to export this information to CSV.
I did this is two parts.
1. Host to Cluster and DataCenter;
2. Network configuration info;
I did this is two parts.
1. Host to Cluster and DataCenter;
Get-VMHost | Select Name, @{N=”Cluster”;E={Get-Cluster -VMHost $_}},@{N=”Datacenter”;E={Get-Datacenter -VMHost $_}} | Export-csv c:\temp\inventory.csv
2. Network configuration info;
&{foreach($esx in Get-VMHost){
$vNicTab = @{}
$esx.ExtensionData.Config.Network.Vnic | %{
$vNicTab.Add($_.Portgroup,$_)
}
foreach($vsw in (Get-VirtualSwitch -VMHost $esx)){
foreach($pg in (Get-VirtualPortGroup -VirtualSwitch $vsw)){
Select -InputObject $pg -Property @{N="ESX";E={$esx.name}},
@{N="vSwitch";E={$vsw.Name}},
@{N="Active NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.ActiveNic)}},
@{N="Standby NIC";E={[string]::Join(',',$vsw.ExtensionData.Spec.Policy.NicTeaming.NicOrder.StandbyNic)}},
@{N="Portgroup";E={$pg.Name}},
@{N="VLAN";E={$pg.VLanId}},
@{N="Device";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Device}}},
@{N="IP";E={if($vNicTab.ContainsKey($pg.Name)){$vNicTab[$pg.Name].Spec.Ip.IpAddress}}}
}
}
}} | Export-Csv "c:\temp\report.csv" -NoTypeInformation -UseCulture
Subscribe to:
Posts (Atom)