REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters\ /v AllowEncryptionOracle /t REG_DWORD /d 2

Enabling Cisco VPN client installation in windows 10 and then handling 442, Failed to enable virtual adapter

1. Install the “SonicWALL Global VPN Client” from http://help.mysonicwall.com/Applications/vpnclient/
prior to installing the Cisco VPN 64 bit client on Windows 10.

2. now install VPN client

3. Try connecting to your destination, you may get a error 442, Failed to enable virutal adapter

4. If you get error in the above step then do the below registry edit.

RegEdit- go to: HKEY_LOCAL_MACHINE>SYSTEM>CurrentControlSet>Services>CVirtA

Edit: DisplayName value from

remove the content like @oem19.inf,%CVirtA_Desc%; 

which is before the Cisco VPN..

Then try connecting , viola it works!!!!

Thanks to all my friends who helped me in configuring this, especially Syed Abdul Rawoof.

Create Login in Logshipping (esp. for Read-only mode DB) or Mirroring DB same as in Primary

Get the login SID info from the primary DB using sp_help_revlogin. Then run the create user with the SID info in the Secondary.

sp_help_revlogin 'loginname

Example output is
CREATE LOGIN [loginname]

WITH PASSWORD = 0x0 HASHED, SID = 0x89C64364B6A88A4A944B3FFB29D42B53,

DEFAULT_DATABASE = [default_db], CHECK_POLICY = ON/OFF, CHECK_EXPIRATION = ON/OFF'

  If the created login has access to other DB's then use sp_change_users_login to fix those orphaned users.

Refer to transfer logins between different SQL servers for more options to move it.

http://support.microsoft.com/kb/246133

Windows 7 - nW adapter priority

How to change the Network Adapter priority in Windows 7 / 2008 R2?

1. Click the Start Button


2. Right Click "Network" and then left Click Properties

3. From the "Network And Sharing Center" window click "Change Adapter Settings"

4. On the "Network Connections" window, press the ALT key on your keyboard to being up the menu bar

5. Click the "Advanced" menu and then "Advanced Settings"

6. In the "Advanced Settings" window you will see the "Adapters and Bindings" tab and under "Connections" you will see the order they are in, you can use the arrows to the side to move the connection priority up and down.



It will still connect all 3, unless you tell it to disable them....but at least traffic will go over the ethernet port first (when connected)

JIT Debugger disable

In the web servers, we end up many times with server out of memory exception, especially where I have heavy web apps and many worker threads configured, mostly due to the vs7jit.exe process.

So to disable the JIT debugger, delete or rename the following keys in the registry( create a backup before proceeding )
•HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger

•HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger

Log shipping copy fails to copy the log to a new secondary server setup

Before few days I setup a new secondary server for the existing Logshipping setup and found that the Log shipping copy fails to copy the tran log files to the new server.
The issue was that the SQL server and its agent service in the new secondary was running with Local System account, hence did not have the permission to copy the file using IPC. When i changed this to a Domain service account which is the same as in primary server, things started working.

Change Log Shipping Monitor Server - SQL 2000

The below content is reused from http://www.sqlservercentral.com/Forums/Topic289235-9-1.aspx

The steps were executed by me and it works.

The steps are described as below
1. Script the "Log Shipping Alert - Backup" and "Log Shipping Alert -
Restore" jobs from the current monitor server
2. Run the following query on current monitor server and save the output -
select maintenance_plan_id from msdb.dbo.log_shipping_primaries
select secondary_plan_id from msdb.dbo.log_shipping_secondaries
3. Execute the scripts created in Step 1 on the new monitor server (in MSDB)
4. Execute the following stored proc on the new monitor server -
sp_add_log_shipping_primary
@primary_server_name = '' ,
@primary_database_name = ''
,@maintenance_plan_id = 'in Step 2>'
,@backup_threshold = freq of backup job>
,@threshold_alert = '14420'
,@threshold_alert_enabled = 1
,@planned_outage_start_time = 0
,@planned_outage_end_time = 0
,@planned_outage_weekday_mask = 0


5. Execute the following select statement to get the Primary_ID in the new monitor server-
select primary_id from msdb.dbo.log_shipping_primaries where
primary_server_name =
'' and primary_database_name = 'name>'
6. Execute the following stored procedure on the new monitor server with the appropriate Secondary Server, and Second db_name and plan_id derived from the select stmt of the current monitor server, for each of the seconday the same needs to be repeated -
sp_add_log_shipping_secondary @primary_id =
, @secondary_server_name = ''
, @secondary_database_name = ''
, @secondary_plan_id = ''
, @copy_enabled = 1
, @load_enabled = 1
, @out_of_sync_threshold = times the freq of copy/restore jobs>
, @threshold_alert = '14421'
, @threshold_alert_enabled = 1
, @planned_outage_start_time = 0
, @planned_outage_end_time = 0
, @planned_outage_weekday_mask = 0
7. Execute the following statement on the Primary and secondary servers to
get the current monitor login information. Verify that you have 1 for logon
type before proceeding with step
8. If you do not have this field set to 1,
then for the time being we will change the authentication mode to NT and
then we can change this later on once the monitor is completely migrated -
select * from msdb.dbo.log_shipping_monitor
go
8. Execute the following command on both Primary and all secondary servers
to change the monitor information -
delete from msdb.dbo.log_shipping_monitor
go
sp_define_log_shipping_monitor '', 1, NULL, 1
go
9. This should complete the migration. Test that the monitor server icon
thing appears under Management tree (Enterprise Manager). When you click
this Log Shipping Monitor, there should be the new pair that you just
added. Once the jobs are working successfully the last copied/loaded file
field will be updated to reflect the changes.


--------------------------------------------------------------------------------

Scott Duncan