Comments for Notes on IT (mainly Microsoft)https://adamsync.wordpress.com
Tue, 06 Nov 2012 20:54:15 +0000hourly1http://wordpress.com/Comment on Microsoft Windows 8 and Cisco Wireless LAN Controller incompatibility by adamsynchttps://adamsync.wordpress.com/2012/09/05/microsoft-windows-8-and-cisco-wireless-lan-controller-incompatibility/#comment-210
Tue, 06 Nov 2012 20:54:15 +0000http://adamsync.wordpress.com/?p=330#comment-210The updates are for Cisco Wireless LAN Controllers; so if they are using those they will need to update them. Some Windows 8 machines will be able to connect if they are running a non-Windows 8 driver for their WiFi card. If you could find a Windows 7 driver for your device that would likely work but the best approach would be to raise a support ticket with the University IT service and draw attention to the available information and ask them about their upgrade plans (assuming that they are using Cisco).
]]>Comment on Microsoft Windows 8 and Cisco Wireless LAN Controller incompatibility by Alessandrohttps://adamsync.wordpress.com/2012/09/05/microsoft-windows-8-and-cisco-wireless-lan-controller-incompatibility/#comment-208
Tue, 06 Nov 2012 00:00:11 +0000http://adamsync.wordpress.com/?p=330#comment-208Do the software trains need to be applied to the routers or the actual computer that is trying to connect to the network? I have an issue connecting to my universities WPA2 AES network now that I have switched to windows 8. Is there anything I can do about it on my end or am I stuck waiting for the IT to catch up the routers? Thanks
]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by Jeroenhttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-19
Wed, 25 Aug 2010 16:57:55 +0000http://adamsync.wordpress.com/?p=27#comment-19The space between the two dashes has to be filled up with the name of your ADAM instance.

I’ve had contact with Microsoft Support and they provided me with this registry key.

]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by adamsynchttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-17
Fri, 20 Aug 2010 16:31:51 +0000http://adamsync.wordpress.com/?p=27#comment-17I have not had a chance to try the patch yet. The registry path above does not look complete is there an element missing? Also how did you figure out that this key was required? Thanks.
]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by Jeroenhttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-16
Thu, 19 Aug 2010 15:22:54 +0000http://adamsync.wordpress.com/?p=27#comment-16Ok everyone, replication is working here. It seems that there was a registry key missing in order to get it going.

]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by Jeroenhttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-15
Wed, 18 Aug 2010 09:13:30 +0000http://adamsync.wordpress.com/?p=27#comment-15Has anyone tried it yet with the patch installed? I’ve set it up here in the lab, but I’m getting the same results i.e. Data could not be decrypted.
]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by adamsynchttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-9
Thu, 01 Jul 2010 09:25:26 +0000http://adamsync.wordpress.com/?p=27#comment-9The best information that I have is that a hotfix is now expected in August (updated in the post above).
]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by gap516https://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-8
Mon, 14 Jun 2010 20:34:31 +0000http://adamsync.wordpress.com/?p=27#comment-8I’m also having the same problem, do you know if MS make a decision on this matter?

Thanks.

]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by Jeroenhttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-7
Sat, 10 Apr 2010 12:53:52 +0000http://adamsync.wordpress.com/?p=27#comment-7Thank you very much for the response. I’ll suggest this as a possibility for the migration. It’s a rather lengthy operation though 🙂

Thanks

]]>Comment on Windows Server 2003 ADAM to Windows Server 2008 AD LDS replication fails when using NTLM (negotiate) by adamsynchttps://adamsync.wordpress.com/2010/04/02/windows-server-2003-adam-to-windows-server-2008-ad-lds-replication-fails-when-using-ntlm-negotiate/#comment-6
Fri, 09 Apr 2010 13:05:41 +0000http://adamsync.wordpress.com/?p=27#comment-6The use of replication as migration path when in a workgroup is exactly what is blocked by this issue. The only “workaround” is to domain join the machines but that may not be an option. There is no supported way to pick up the database from an ADAM instance and present it to an AD LDS instance however perhaps you could consider the following:

take a backup [1] of your ADAM instance (hopefully you backup anyway).
Note to have a portable backup (for restore to another server) it’s usually a good idea to add the Windows Builtin Administrators group to the Administrators role in the ADAM instance if not already present (you can remove it again after taking the backup if required)

install a Win2k3 server on some machine (physical or virtual) and install ADAM and then restore your ADAM backup to that server

upgrade that Win2k3 server just created to Win2k8 and upgrade the ADAM instance to AD LDS [2] for testing