Cisco Tuning Adapters and the Ceton card

This article describes that the Cisco Tuning adapters I received from Time Warner cable should be hooked up in Parallel and not serial like Time Warner told me. The Tuning adapters do not support the pass-through port when connecting multiple TAs. You should be using a 3 way or 4 way splitter in order to split the cable connection and have an individual cable go to each TA and the tuner card.

I hope that helps out somebody else as well.

Thanks,
Andreas

After a longer research into the issue I found this Microsoft KB.

In there Microsoft informs about how WebDav secures sites or networks. I always knew that SharePoint uses WebDav to share documents to Office applications however I had no idea that you had to specify a trusted location if it uses an Internet FQDN instead of a local netbios name.

So I followed the KB and I actually deloyed the registry key via Group Policy Prefferences and after people restarted their PCs no more calls about having to authenticate.

Thanks,

Andreas

The command line over the serial connection didn't allow me to set the IP or anything so I did a quick Google and came across this article.

In there I found that the 28xx series switches use a default IP of 192.168.2.1. I browsed there and was able to login with admin and no password. This allowed me to fully set them up.

I hope that this helps somebody else too.

Thanks,

Andreas

First run this Query:

USE master
GO
IF OBJECT_ID ('sp_hexadecimal') IS NOT NULL
DROP PROCEDURE sp_hexadecimal
GO
CREATE PROCEDURE sp_hexadecimal
@binvalue varbinary(256),
@hexvalue varchar (514) OUTPUT
AS
DECLARE @charvalue varchar (514)
DECLARE @i int
DECLARE @length int
DECLARE @hexstring char(16)
SELECT @charvalue = '0x'
SELECT @i = 1
SELECT @length = DATALENGTH (@binvalue)
SELECT @hexstring = '0123456789ABCDEF'
WHILE (@i <= @length)
BEGIN
DECLARE @tempint int
DECLARE @firstint int
DECLARE @secondint int
SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1))
SELECT @firstint = FLOOR(@tempint/16)
SELECT @secondint = @tempint - (@firstint*16)
SELECT @charvalue = @charvalue +
SUBSTRING(@hexstring, @firstint+1, 1) +
SUBSTRING(@hexstring, @secondint+1, 1)
SELECT @i = @i + 1
END

SELECT @hexvalue = @charvalue
GO

IF OBJECT_ID ('sp_help_revlogin') IS NOT NULL
DROP PROCEDURE sp_help_revlogin
GO
CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS
DECLARE @name sysname
DECLARE @type varchar (1)
DECLARE @hasaccess int
DECLARE @denylogin int
DECLARE @is_disabled int
DECLARE @PWD_varbinary  varbinary (256)
DECLARE @PWD_string  varchar (514)
DECLARE @SID_varbinary varbinary (85)
DECLARE @SID_string varchar (514)
DECLARE @tmpstr  varchar (1024)
DECLARE @is_policy_checked varchar (3)
DECLARE @is_expiration_checked varchar (3)

DECLARE @defaultdb sysname

IF (@login_name IS NULL)
DECLARE login_curs CURSOR FOR

SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name <> 'sa'
ELSE
DECLARE login_curs CURSOR FOR

SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM
sys.server_principals p LEFT JOIN sys.syslogins l
ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name = @login_name
OPEN login_curs

FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
IF (@@fetch_status = -1)
BEGIN
PRINT 'No login(s) found.'
CLOSE login_curs
DEALLOCATE login_curs
RETURN -1
END
SET @tmpstr = '/* sp_help_revlogin script '
PRINT @tmpstr
SET @tmpstr = '** Generated ' + CONVERT (varchar, GETDATE()) + ' on ' + @@SERVERNAME + ' */'
PRINT @tmpstr
PRINT ''
WHILE (@@fetch_status <> -1)
BEGIN
IF (@@fetch_status <> -2)
BEGIN
PRINT ''
SET @tmpstr = '-- Login: ' + @name
PRINT @tmpstr
IF (@type IN ( 'G', 'U'))
BEGIN -- NT authenticated account/group

SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' FROM WINDOWS WITH DEFAULT_DATABASE = [' + @defaultdb + ']'
END
ELSE BEGIN -- SQL Server authentication
-- obtain password and sid
SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, 'PasswordHash' ) AS varbinary (256) )
EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT
EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT

-- obtain password policy state
SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name
SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name

SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' WITH PASSWORD = ' + @PWD_string + ' HASHED, SID = ' + @SID_string + ', DEFAULT_DATABASE = [' + @defaultdb + ']'

IF ( @is_policy_checked IS NOT NULL )
BEGIN
SET @tmpstr = @tmpstr + ', CHECK_POLICY = ' + @is_policy_checked
END
IF ( @is_expiration_checked IS NOT NULL )
BEGIN
SET @tmpstr = @tmpstr + ', CHECK_EXPIRATION = ' + @is_expiration_checked
END
END
IF (@denylogin = 1)
BEGIN -- login is denied access
SET @tmpstr = @tmpstr + '; DENY CONNECT SQL TO ' + QUOTENAME( @name )
END
ELSE IF (@hasaccess = 0)
BEGIN -- login exists but does not have access
SET @tmpstr = @tmpstr + '; REVOKE CONNECT SQL TO ' + QUOTENAME( @name )
END
IF (@is_disabled = 1)
BEGIN -- login is disabled
SET @tmpstr = @tmpstr + '; ALTER LOGIN ' + QUOTENAME( @name ) + ' DISABLE'
END
PRINT @tmpstr
END

FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin
END
CLOSE login_curs
DEALLOCATE login_curs
RETURN 0
GO

This creates two stored procedures in the master database.

To actually use the stored procedure to create a script for us you need to be logged in with a user that has the SQL server sysadmin role.

If you have that role go ahead and run:

EXEC sp_help_revlogin

as a new Query.

The result of the query should be a SQL query script that creates the logins on the new server. Before I ran it on the new server I deleted all the logins that already exist for example my own, local system and etc.

Now you only have to be sysadmin on the new SQL instance so you can run the script on there and you should be all set.

I hope it works for you as good as it did for me

Andreas

Once installed you can simply set the software to use the Bluetooth GPS and publish it one or more COM ports.

If you are not going to do anything crazy and really only want the software for Mappoint or Streets and Trips you can use the Express version which won’t cost you too much. So here is the link to the client:

http://gpsgate.com/products/gpsgate_client

And here is the link to the purchase page for the Express version:

http://gpsgate.com/purchase/gpsgate_express_license

I hope it works for you as it has for me

Andreas

Anyway I found these three articles that really cleared things up:

Part 1

Part 2

Part 3

In these three articles they cover everything you will need to know about load balancing the two servers. It is quite simple actually. Install all roles on both servers. Now you will have to edit the registry to not use a dynamic port for RPC which is used by IMAP and Directory Access:

On the CAS servers, for Mailbox connections, you need to use add a DWORD registry key named “TCP/IP Port” under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRpc\ParametersSystem

Figure 8: Adding the required DWORD key on CAS server to configure a static port number

Set the value to the port number to be assigned. In this article we use port 55000, but you are free to choose whatever port you want to use, just remember it should not conflict with other applications using the port. It is recommend you choose a port within the dynamic RPC ranger (1024-65535).

This is from Part 2.

If you set this on both the servers you will need a lot less ports to load balance then before. I am basing this on Kentrox LoadMasters. They are a great product but the only thing they are missing right now is load balancing port ranges. This of course is no big deal after using the registry edit to change it from a dynamic port range to a single static port.

If you have different load balancers you might be able to just load balance the entire servers but it doesn’t matter if you do or not.

Also very good information is in Part 1 about Persistence and in Part 3 about the exact settings of the Kentrox Load Masters.

I also discovered a great website from Microsoft which can help you test outside Exchange connectivity. I know it supports Exchange 2010 but it might work for 2007 as well. Even if the site is made my Microsoft I would for sure not use an account that is actually going to be used with this site. Anyway here is the site and it pretty much tests anything you could.

https://www.testexchangeconnectivity.com/

I hope you have fun,

Andreas

So I stated researching and found the following post:

http://arstechnica.com/civis/viewtopic.php?f=11&t=327353

In this post they are describing a very similar issue. They are also talking about that the solution is using a PCL driver (which by the product description it natively supports). However HP is unique in this case. They don’t actually have a PCL driver for this printer they only have a Host Based printer driver.

They requested help from HP who actually told them to use a HP LaserJet 6L driver.

So by this answer from HP we can see that they are obviously aware of the problem but decided not to fix it and give a work around instead.

It works perfectly fine to use the LaserJet 6L driver. If you can’t see the driver when installing the printer you can press Windows Update in Windows 7 and Vista in order for it download a lot of drivers from Windows Update.

I hope this helps somebody

Andreas

If you want more and your computer has its pagefile on the C drive it will try to create a Crash dump Memory file under C:\Windows called Memory.dmp

This file you can analyze. I followed this instructions:
http://www.brighthub.com/computing/windows-platform/articles/29860.aspx

However you can simplfy this:

Go to this page: http://www.microsoft.com/downloads/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b&displaylang=en

Download the utility and run it. It will automatically detect the right version and guide you through the install.

On this screen only select the Common Utilities (I installed the Redistributable packages as well just to make sure everything works)

After it downloads and installs everything go into your start menu and open up WinDbg. Now click on File - Symbol File path and paste the following into the window:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

and click ok.

Now just open the crash dump .dmp file with file - open crash dump. Once analyzed it will let you know what file it thinks the problem file was.
( I in the past had a lot of luck when there were corrupt or buggy drivers on the system) If you end up with a .sys file you can usually Google it to find out what driver it is.

When it is down with analyzing you can click on the links in blue to get more inept (hint the "!analyze -v" is very helpful)

I hope that helps somebody with a BSOD problem

Andreas

UPDATE:

Correction from before: The only thing required to run the debugging  tools is the actual debugging tools under Common Utilities. Also the .net 4.0 is not required.

http://poseidom.wordpress.com/2007/12/16/set-spn-for-sql-2005-sccm-remote-sql-fix/

I know it is for SQL 2005 however it works on SQL 2008 and R2 just as well and I would actually say you should do that with every SQL server, that uses a domain service account, you got because sooner or later you will run into that problem.

I actually did the Method 2 on his blog because i might want some more instances and i don't want to worry about SPNs any more! (also for teh 2nd Method you don't need the port numbers)

Method 1: The “Right” way

1. Install the Windows 2003 support tools somewhere on a machine in the domain
2. Login as a Domain Admin
3. Run  setspn -A MSSQLSvc/<FQDN> <SQL_Service_Account> Note YOU MUST USE THE FQDN
4. Run  setspn -A MSSQLSvc/<FQDN>:<Port> <SQL_Service_Account>  Note YOU MUST USE THE FQDN, and the most common port is 1443
5. Run setspn -L <SQL_Service_Account> validate that “servicePrincipalName:” has been set like you expect
6. Restart the SQL server after AD replication has completed
7. Run the following query on the SQL server; this MUST return KERBEROS:
   select auth_scheme from sys.dm_exec_connections where session_id=@@spid

Method 2: The “easy” way

In adsiedit grant the service account the ability to write the servicePrincipalName to “SELF”
Taken from: http://support.microsoft.com/kb/319723

• 1. Click Start, click Run, type Adsiedit.msc, and then click OK.
     • Note The ADSIEdit tool is included in the Windows Support Tools. To obtain the Windows Support Tools, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?familyid=6EC50B78-8BE1-4E81-B3BE-4E7AC4F0912D&displaylang=en
  2. In the ADSI Edit snap-in, expand Domain [DomainName], expand DC= RootDomainName, expand CN=Users, right-click CN= AccountName , and then click Properties.
     • DomainName is a placeholder for the name of the domain.
     • RootDomainName is a placeholder for the name of the root domain.
     • AccountName is a placeholder for the account that you specify to start the SQL Server service.
     • If you specify the Local System account to start the SQL Server service, AccountName is a placeholder for the account that you use to log on to Microsoft Windows.
     • If you specify a domain user account to start the SQL Server service, AccountName is a placeholder for the domain user account.
  3. In the CN= AccountName Properties dialog box, click the Security tab.
  4. On the Security tab, click Advanced.
  5. In the Advanced Security Settings dialog box, make sure that SELF is listed under Permission entries.
     • If SELF is not listed, click Add, and then add SELF.
  6. Under Permission entries, click SELF, and then click Edit.
  7. In the Permission Entry dialog box, click the Properties tab.
  8. On the Properties tab, click This object only in the Apply onto list, and then click to select the check boxes for the following permissions under Permissions:
     • Read servicePrincipalName
     • Write servicePrincipalName
  9. Click OK two times.

Of course the first method is more secure and probably better for most environments but if your environment is like mine where stuff changes every week I would go with Method 2.

Anyway now both SCCM and VMM are happy like never before. They like not having a SQL server on the same box.

Andreas

This is the script:

CREATE PROC BackupDatabase (
@DatabaseName sysname ,
@SQLBackupFolder nvarchar(400)
)
AS

DECLARE @BackupSQLScript nvarchar(max)
DECLARE @SQLBackupFileName nvarchar(400)

SET @SQLBackupFileName =
REPLACE(@DatabaseName,' ','-') +
CONVERT(VARCHAR,GETDATE(),112) + '.bak'

SET @BackupSQLScript = '
BACKUP DATABASE [' + @DatabaseName + ']
TO DISK = ''' + @SQLBackupFolder + @SQLBackupFileName + ''''

print @BackupSQLScript
EXEC sp_executesql @BackupSQLScript
GO

I simply edited that it inserts a dash between DB name and date for the file name:

CREATE PROC BackupDatabase (
@DatabaseName sysname ,
@SQLBackupFolder nvarchar(400)
)
AS

DECLARE @BackupSQLScript nvarchar(max)
DECLARE @SQLBackupFileName nvarchar(400)

SET @SQLBackupFileName =
REPLACE(@DatabaseName,' ','-') + (' - ') +
CONVERT(VARCHAR,GETDATE(),112) + '.bak'

SET @BackupSQLScript = '
BACKUP DATABASE [' + @DatabaseName + ']
TO DISK = ''' + @SQLBackupFolder + @SQLBackupFileName + ''''

print @BackupSQLScript
EXEC sp_executesql @BackupSQLScript
GO

After running this you have the stored procedure in your instance and therefore you will be able to run the actual backup script:

EXEC sp_Msforeachdb "
DECLARE @BackupFolder nvarchar(400);
SELECT @BackupFolder = 'C:\backups\';
EXEC BackupDatabase '?', @BackupFolder
"

Oh yeah don't forget to replace C:\backups\ with the folder you want to backup to. (and also don't forget the backslash at the end!!)

Oh and almost forgot if you don't know how to backup just one DB through the Management studio here is a link from that same site:

http://www.kodyaz.com/articles/sql-backup-sql-server-backup-database.aspx

And have fun backing up or moving DBs

Andreas