I have SharePoint 2010 set up to sync active directory users and it is working great. I am getting disabled users in the sync though. I have tried what all the blogs say, filter on
userAccountControl bit on equals 2
but to no avail, the disabled users are still syncing. I am at a loss on where to look next. My last resort would be to create a ou/folder in AD and move disabled users there and remove that from the sync connector, but I don't really want to go there.
Any ideas?
i have 3 servers, all relatively the same hardware/config, etc. I run some data pulls on all 3, and on 2 of them, they have 1 nic, and they work fine. On the other , there are 2 nics, and unless they are both plugged in or teamed, the processes time out.
Any ideas on why this would be? It doesn't make sense to me, as the other two work fine with 1 nic and don't time out when running the same processes.
Running into a very weird issue. Converting servers to Windows 2008/SQL 2008. Have a server, SERVER_A, brand new, setup with Win2k8,Sql2k8 - works. Have a Server SERVER_B, running Windows2003/SQL2005. I want to migrate from SERVER_B to SERVER_A. I have all db's, cubes, etc setup on SERVER_A and it is mimicking functionality.
Since users are using Excel to connect to SSAS, they connection string has SERVER_B in it. What I want to do, is, change DNS on the network to point SERVER_B (by name) at the ip of SERVER_A.
I have successfully done this with another server, SERVER_C, but I need to do it with SERVER_B.
What I have found is that with SERVER_C, after changing DNS, had to remove SERVER_C from AD and then it worked. I could connect to SERVER_C (DB), SERVER_C (SSAS Default Instance) and SERVER_C (SSAS Named instance) and it all was actually connecting to SERVER_A
I tried to do the same with with SERVER_B, and no luck. Changed DNS, removed from AD, and it wouldn't connect. Found out that there were some SPN's in AD set up, so removed those and tried again.
I then could connect to SERVER_B (DB), SERVER_B (SSAS Named Instance), but not SERVER_B (SSAS Default Instance). I could connect to SERVER_B (SSAS Default Intance WITH the Port #), but I need to be able to connect without the port number.
I am at a loss to as why I can't connect to the default instance without a port #. Not sure if it is SPN's in AD, or another AD issue, or something else. Pretty sure it isnt something on the server (because SERVER_C works!)
Any insight or suggestions would be greatly helpful!!
I have used the Cisco VPN client for years, and on XP it is pretty much rock solid, on Vista, not so much. You might be able to connect, but unless you set up a constant ping to something, it usually will disconnect, with this error:
Reason 442: Failed to enable Virtual Adapater
Now, most sysadmins will say, update you client - yes, I know, it hasnt mitigated the issue, ever. I have been using it on Vista since it came out, and updated my client every time a new update comes out.
I have used it where the VPN server was a Cisco PIX and a Windows Box allowing the Cisco Client to connect.
Anyone have any fixes that you can do on your client to fix this issue?
Using data integrator for ETL's pulling data from DB2 to SQL Server, after some time, will get these odbc errors:
Communication link failure. comm rc=10055 - CWBCO1003 - Sockets error, function returned 10055
Can't do anything with ODBC after that, have to reboot the box, and currently we just reboot the box every night at midnight to try to avoid the issue from happening.
Tried this, http://support.microsoft.com/kb/196271 but it didn't work, almost made it worse.
There doesn't seem to be a solution in sight. No other boxes that use ODBC get this issue that we use. Can't reformat the box at this time, legacy stuff on it.
Has anyone seen this issue, come across it, fixed it, mitigated it?