An error occurred while making the requested connection and there was an error in the application log for each time I tried to connect.

The Citrix servers reported that they are too busy to provide access to the selected resource. This message was reported from the XML Service at address <http://servername:xml_port>

Let’s call Citrix Technical Support, oh wait we don’t have support so let’s figure it out. Everywhere I looked people were saying it was a licensing issue. I tried everything I read

Add one or more servers to the Worker Group assigned to the published application.

If no applications are published to a Worker Group, check to see that logins are not disabled to the server. If they are, re-enable logins.

The server the application is published on does not have a load evaluator assigned. This can be seen in QFARM:

From the Citrix Delivery Services Console:

- Right click on the server and select Other Tasks | Assign Load Evaluator from the context menu.

The load will go to 10000, and then settle after a couple of minutes:

SURE

Running the qfarm / load command I was seeing 20000 as all of the posts say is BAD.

Checking HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\ProductFeature like one article I read and it was blank. Now what?

I had to modify the unfiltered XenApp policy for License Server Host Name

1.       In the Delivery Services Console, navigate to the Policies node and select the Computer tab and Unfiltered policy.

2.       Click the Settings tab in the lower pane.

3.       In the Search All Settings search field, type License.

4.       Add or Edit the License server hostname or License server port or both settings.

5.       Run GPUPDATE /FORCE.

6.       Restart Independent Management Architecture service.

7.       Run QFARM /LOAD.

8.       Verify that the server load reverts back to zero.

Mine didn’t, there was one more thing that did it for me. I then had to duplicate the default load evaluator and then assigned the new copy of the default load evaluator to the XenApp Server.

Run QFARM /LOAD.

Wait for a few seconds and you should be in business. My new XenApp 6 Farm is now accepting connections.

“The desktop you are trying to open is currently available only to administrators. Contact your administrator to confirm that the correct settings are in place for your client connection.”

“You do not have access to logon to this Session.”

These messages appear even though the user is a member of the Remote Desktop Users group.

The user does has not have problems connecting with a MetaFrame Presentation Server Client for 32-bit Windows.

Cause

Installing MetaFrame Presentation Server 3.0 on a Windows Server 2003 creates a new RDP-TCP listener. The default properties of this listener allow only the launching of published applications.

Resolution

To allow users to connect with an RDP connection, clear Only launch Published Applications under the Advanced Connection settings of the RDP-TCP listener.

To resize desktop icons
• Right-click the desktop, point to View, and then click Large Icons, Medium Icons, or Classic Icons. (Classic icons are the smallest size.)

You can also use the scroll wheel on your mouse to resize desktop icons. On the desktop, press and hold CTRL while you scroll the wheel to make icons larger or smaller.

This issue occurs because the non-administrator user account cannot access the %WINDIR%\System32 folder. By default, WPF writes the output file to the %WINDIR%\System32 folder. The %WINDIR%\System32 folder requires administrator permissions. When the non-administrator account tries to access this folder, the WPF caching code is triggered. This code causes the screen to flicker. 

In 32-bit versions of the Windows Server 2003 operating system, the output file is D3d9caps.dat. In 64-bit versions of the Windows Server 2003 operating system, the output file is D3d9caps64.dat.

To resolve this problem, install the following hotfix. After you install this hotfix, WPF applications write the output file to the current user profile instead of to the %WINDIR%\System32 folder.

See http://support.microsoft.com/kb/955692 for more details

• You use a non-administrator user account to connect to a Windows Server 2003-base terminal server by using a third-party terminal client, such as a Citrix ICA client.
• You run Windows Presentation Foundation (WPF) applications in the terminal server session.

In this scenario, you may notice that your screen flickers. You do not encounter this issue when you use Remote Desktop Connection (RDC) to create the terminal server session

Please follow the appropriate procedure for your server.
For OfficeScan 10 running IIS
1.	Run the following command in the drive\Trend Micro\Office SCAN\PCCSRV\ folder using DOS Prompt:
			Svrsvcsetup.exe -uninstall
	Note: OfficeScan Server will not function while performing cloud scan server (integrated) reactivation. Only the related OfficeScan services will be uninstalled. Configuration and database will still be kept.
2.	Modify the following keys in the drive\Trend Micro\Office SCAN\PCCSRV\private\ofcserver.ini file:
	[TMCSS]
	·	WSS_INSTALL=1
	·	WSS_ENABLE=1
	·	WSS_URL=https://tw-machinename:4345/tmcss/
	·	WSS_HTTP_URL=http://tw-machinename:8082/tmcss/
	Note: SSL port will be based on the selected web server that is used for the OfficeScan server.
3.	Modify the following keys in the drive\Trend Micro\Office SCAN\PCCSRV\OfUninst.ini file:
	·	[WSS_VIRDIR_INFO]
		ROOT=/tmcss,C:\Program Files\Trend Micro\OfficeScan\PCCSRV\WSS\isapi,,5
	·	[WSS_WEB_SERVER]
		ServerPort=8082
		IIS_VhostName=Cloud Scan Server (Integrated)
		IIS_VHostIdx=5   Note: IIS_VHostidx= “5” must have same number as isapi,,”5”
	·	[WSS_SSL]
		SSLPort=4345   Note: SSL port will be based on the selected web server that is used for the OfficeScan server.
For OfficeScan 10 running Apache
1.	Run the following command in the drive\Trend Micro\Office SCAN\PCCSRV\ folder using DOS Prompt:
			Svrsvcsetup.exe -uninstall
	Note: OfficeScan Server will not function while performing cloud scan server (integrated) reactivation. Only the related OfficeScan services will be uninstalled. Configuration and database will still be kept.
2.	Modify the following keys in the drive\Trend Micro\Office SCAN\PCCSRV\private\ofcserver.ini file:
	[TMCSS]
	·	WSS_INSTALL=1
	·	WSS_ENABLE=1
	·	WSS_URL=https://tw-machinename:4343/tmcss/
	·	WSS_HTTP_URL=http://tw-machinename:8080/tmcss/
	Note: SSL port will be based on the selected web server that is used for the OfficeScan server.
3.	Modify the following keys in the drive\Trend Micro\Office SCAN\PCCSRV\OfUninst.ini file:
	·	[WSS_VIRDIR_INFO]
		ROOT=/tmcss,C:\Program Files\Trend Micro\OfficeScan\PCCSRV\WSS\isapi,,5
	·	[WSS_WEB_SERVER]
		ServerPort=8080
	·	[WSS_SSL]
		SSLPort=4343   Note: SSL port will be based on the selected web server that is used for the OfficeScan server.
4.	Run the following commands in the drive\Trend Micro\Office SCAN\PCCSRV\ folder using DOS Prompt:
	·	Svrsvcsetup -install
	·	Svrsvcsetup -enablessl
	·	Svrsvcsetup -setprivilege
5.	Check for the following:
	·	Trend Micro Cloud Scan Server is started with manual mode
	·	Cloud Scan Server related performance counters are registered
	·	Send a CRC query to Cloud Scan Server

Please do the following:
1.	Copy the ipXfer.exe tool from the OfficeScan server:
		c:\…\Pccsrv\admin\utility\ipxfer\ipxfer.exe
		Note: This is only for fresh install of OfficeScan 3.53 and above.
2.	Run the ipxfer.exe tool on a workstation or copy the file to an existing OfficeScan network server directory \\<OfficeScan server>\ofcscan.
3.	Make sure that all users have executable access to the ipxfer.exe file on the server.
4.	Go to the network directory where the ipXfer.exe file has been copied.
5.	Open a command prompt and then execute the following:
		ipXfer.exe -m 1 -s < server > -p < IIS_TCP_port > -c < client_listening_port > -q 1
	Note: The -s and -c parameters should not contain the <> brackets. The -q switch only applies to the newer version of ipXfer.exe included in OfficeScan 5.5 and above.
	Here are the values of the switches:
	·		-m <installation mode>
			1- >HTTP-based 0- >File-based
	·		-s <server>
			[server_FQDN| server_WINS_name| server_IP_address | UNC_Path_to_Server]
			The correct value of this parameter is provided by the “MASTER_DOMAINNAME” value in the ..\pccsrv\ofcscan.ini file on the target server.
	·		-p <IIS_TCP_Port>
			The default value when using the IIS Default Website is 80, and 8080 when using the IIS Virtual Website.
			To identify the correct value for the IIS_TCP_Port, do the following:
			a.	Check the IIS Management Console> Default Web site properties > TCP port
				or
			b.	Check the ..\pccsrv\ofcscan.ini file for the "MASTER_DOMAINPORT" value on the target server.
	·		-c <OfficeScan client listening port>
			Check the OfficeScan server directory c:\..\pccsrv\ofcscan.ini for the "CLIENT_LOCALSERVER_PORT" to match the parameters.
	·		-q <internet settings force-change switch>
			This should always be set to “1”.
			The older versions of the IPXFER utility are sometimes unable to migrate clients correctly. It was found that the values in the HKEY_LOCAL_MACHINE\Software\TrendMicro\PC-cillinNTCorp\Internet Settings registry hive still reflect the previous server. Setting the value to “1” forces the changes in the registry.
6.	To ensure the connectivity of the workstation clients to the OfficeScan server, you may insert the IPXFER.EXE command line call into a server, a network login script, or a batch file:
			Example syntax: \\MyServer\ofcscan\ipXfer.exe -m 1 -s MyServer -p 80 -c 12345 -q 1
	Important: The -s switch and its information is necessary to resolve connectivity between OfficeScan servers and workstations.
	To avoid losing the server connection, perform the same process on the OfficeScan console > Server Administration > Web server > Server info.
			When using the IPXFER tool, the -s setting should match the exact setting in the new server’s ofcscan.ini file, including the IP address of the server.
			If these settings do not match, the client workstation may experience conflict that will affect the server.
7.	Modify the IPXFER script to make sure that it matches the OfficeScan server.
	Verify the settings of the OfficeScan server by doing either of the following:
	a.		On the Management console, go to Server Administrator > Web Server section.
			or
	b.		Open the Ofcscan.ini file in the ..\PCCSRV directory and look for the “Master_DomainName=” parameter.
8.	Make sure that the value of the following parameters are correct in both the server and the clients:
	·		MasterDirectory=
	·		Master_DomainName=
9.	Save a copy of the correct ofcscan.ini file in the following directories:
	·		..\PCCSRV\PCCNT\Disk1
	·		..\PCCSRV\PCC95\Disk1
10.	Update the client machine with the configuration and any available pattern file and/or scan engine updates from the new OfficeScan server.
11.	Run the Autopcc.exe file from the new server using either the command line or the login script.

If you know the name of a process to kill, for example notepad.exe, use the following command from a command prompt to end it:

taskkill /IM notepad.exe

This will cause the program to terminate gracefully, asking for confirmation if there are unsaved changes. To forcefully kill the same process, add the /F option to the command line. Be careful with the /F option as it will terminate all matching processes without confirmation.

To kill a single instance of a process, specify its process id (PID). For example, if the desired process has a PID of 827, use the following command to kill it:

taskkill /PID 827

Using filters, a variety of different patterns can be used to specify the processes to kill. For example, the following filter syntax will forcefully kill all processes owned by the user Quinn:

taskkill /F /FI "USERNAME eq JOE"

The following table shows the available filters and their use.

Filter Name Valid Operators Valid Value(s)
----------- --------------- --------------
STATUS eq ne RUNNING | NOT RESPONDING
IMAGENAME eq ne Image name
PID eq ne gt lt ge le PID value
SESSION eq ne gt lt ge le Session number.
CPUTIME eq ne gt lt ge le CPU time in the format
of hh:mm:ss.
MEMUSAGE eq ne gt lt ge le Memory usage in KB
USERNAME eq ne User name in [domain\]user
format
MODULES eq ne DLL name
SERVICES eq ne Service name
WINDOWTITLE eq ne Window title

eq: equals ne: not equal
gt: greater than lt: less than
gt: greater than or equal le: less than or equal

Under PHP you need to use header() to send a raw HTTP header.

Using headers() method, you can easily transferred to the new page without having to click a link to continue. This is also useful for search engines. Remember that header() must be called before any actual output is sent, either by normal HTML tags, blank lines in a file, or from PHP. It is a very common error to read code with include(), or require(), functions, or another file access function, and have spaces or empty lines that are output before header() is called. The same problem exists when using a single PHP/HTML file.

PHP Redirect Script
You can easily redirect using following code:

 
<?php
 /* Redirect browser */
 header("Location: http://www.clevelandcg.com/");
 /* Make sure that code below does not get executed when we redirect. */
 exit;
?>

Another sample hack
Sample function - sitefunctions.php (note I'm not the author of the following I found it somewhere else on the Internet):

function movePage($num,$url){
 static $http = array (
  100 => "HTTP/1.1 100 Continue",
  101 => "HTTP/1.1 101 Switching Protocols",
  200 => "HTTP/1.1 200 OK",
  201 => "HTTP/1.1 201 Created",
  202 => "HTTP/1.1 202 Accepted",
  203 => "HTTP/1.1 203 Non-Authoritative Information",
  204 => "HTTP/1.1 204 No Content",
  205 => "HTTP/1.1 205 Reset Content",
  206 => "HTTP/1.1 206 Partial Content",
  300 => "HTTP/1.1 300 Multiple Choices",
  301 => "HTTP/1.1 301 Moved Permanently",
  302 => "HTTP/1.1 302 Found",
  303 => "HTTP/1.1 303 See Other",
  304 => "HTTP/1.1 304 Not Modified",
  305 => "HTTP/1.1 305 Use Proxy",
  307 => "HTTP/1.1 307 Temporary Redirect",
  400 => "HTTP/1.1 400 Bad Request",
  401 => "HTTP/1.1 401 Unauthorized",
  402 => "HTTP/1.1 402 Payment Required",
  403 => "HTTP/1.1 403 Forbidden",
  404 => "HTTP/1.1 404 Not Found",
  405 => "HTTP/1.1 405 Method Not Allowed",
  406 => "HTTP/1.1 406 Not Acceptable",
  407 => "HTTP/1.1 407 Proxy Authentication Required",
  408 => "HTTP/1.1 408 Request Time-out",
  409 => "HTTP/1.1 409 Conflict",
  410 => "HTTP/1.1 410 Gone",
  411 => "HTTP/1.1 411 Length Required",
  412 => "HTTP/1.1 412 Precondition Failed",
  413 => "HTTP/1.1 413 Request Entity Too Large",
  414 => "HTTP/1.1 414 Request-URI Too Large",
  415 => "HTTP/1.1 415 Unsupported Media Type",
  416 => "HTTP/1.1 416 Requested range not satisfiable",
  417 => "HTTP/1.1 417 Expectation Failed",
  500 => "HTTP/1.1 500 Internal Server Error",
  501 => "HTTP/1.1 501 Not Implemented",
  502 => "HTTP/1.1 502 Bad Gateway",
  503 => "HTTP/1.1 503 Service Unavailable",
  504 => "HTTP/1.1 504 Gateway Time-out"
 );
 header($http[$num]);
 header ("Location: $url");
}

Now call it as follows:

<?php
 @include("/path/to/sitefunctions.php");
 movePage(403,"http://www.clevelandcg.com/");
?>

You can also do this using HTML or Javascript.

Using HTML META tag

<meta http-equiv=”refresh” content=”5;URL=http://www.clevelandcg.com”>

Using Javascript function

function Redirect(url)
{
 location.href = url;
}
This can be called as
Redirect ("http://www.clevelandcg.com");</meta>

ini_set('display_errors',1);
error_reporting(E_ALL|E_STRICT);
or if you only want to see Warning Messages and not Notice Messages:

ini_set('display_errors',1);
error_reporting(E_ALL);
and if you just want all Error Reporting off, simply use this:

error_reporting(0);

To do this in the .htaccess use:
php_flag display_errors on
php_value error_reporting 7

For example use

<div>
     &copy; <? echo date('Y');?> Cleveland Consulting Group. All Rights Reserved
</div>

instead of

<div>
     &copy; <? echo date(Y);?> Cleveland Consulting Group. All Rights Reserved
</div>

If you dont you will receive

Notice: Use of undefined constant Y - assumed 'Y' in FOLDERPATH/FILNAME.php on line #

Open up your .htaccess file using your favorite text editor, if you dont have one then you can create one in the directory where you want the rewriting to happen and type in the following. If you already have RewriteEngine On just paste the rest of the text below what you have.

RewriteEngine On
RewriteRule ^([^.]+)/?$ $1.php?%{QUERY_STRING} [L]

To selectively make certain files redirect you can specify each of them inbetween the () and separate each with a |

RewriteEngine On
RewriteRule ^(index|contact|register|login|yougetthepicture)/?$ $1.php?%{QUERY_STRING} [L]

If that period is within the thresholds that have been set, then there is no problem as you will see later in this post.  However, if you need to maintain the data longer, then you better “restore” the data to a tape, so you can store it away for a longer time.

But, for today, here is the procedure how to remove the ‘dead’ agent

In this screenshot you can see an agent that is not reachable anymore.

So I tried to remove the agent.  I did right click and choose Uninstall

This is the error I’m getting.  The server is still in one of my protection groups, so I can’t remove it until I first remove it from the protection group.

So I’m going to the protection group

Right-click and choose Stop Protection of Group.

Note: In case you want to remove a server out of a protection group, but don’t remove the protection group then you need to modify it.  It will automatically create an Inactive protection for previously protected data in the UI

I choose to delete the protection group and retain the data

After the job, I have an inactive protection for this source

So back to my management, right-click on the dead server and Uninstall

I have to enter my credentials

The agent is being uninstalled

But as said, the server is dead, so this is not going to work.  DPM now asks me if I want to remove the agent record from the database.  I choose Yes

At the end, DPM still tells me that the job has failed, but since I told him to remove the record, it should have done the job after all.  And indeed, the server will not be listed anymore in the UI.

When I go back to protection, I will see that I still have data for that source and still can restore if needed.  Again, don’t forget to restore to somewhere if you need it longer, otherwise the data will be gone after it’s protection period is over

Note
To create, revert to, or delete a database snapshot, you must use Transact-SQL.
 

To view a database snapshot on a server
1.In Object Explorer, connect to the instance of the Microsoft SQL Server Database Engine and then expand that instance.

2.Expand Databases.

3.Expand Database Snapshots, and select the snapshot you want to view.

The replica on SQL Server 2005 database SERVER NAME\DATABASE NAME on SERVER NAME is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106) 

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried, the error is likely to reoccur. (0x800423F4))

Recommended action: Please check that the Event Service, the VSS service and the shadow copy provider service is running, and check for errors associated with these services in the Application Event Log on the server SERVER NAME. Please allow 10 minutes for VSS to repair itself and then retry the operation.

For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.

Synchronize with consistency check.

Run a synchronization job with consistency check...

To dismiss the alert, click below to Inactivate alert

What the error doesnt tell you is you are trying to backup a snapshot. Microsoft says

SQL Server 2005 includes database snapshots that appear in the New Protection Group Wizard as regular databases. However, DPM does not support protecting database snapshots for recovery.

You can log onto you SQL server, open up SQL Server Management Studio,

1.In Object Explorer, connect to the instance of the Microsoft SQL Server Database Engine and then expand that instance.

2.Expand Databases.

3.Expand Database Snapshots, and select the snapshot you want to view.

Now that you have confirmed this is a snapshot you can remove it from your protection group, otherwise you will continue to receive critical alerts everytime the snapshot is scheduled to be backed up. Hopefully Microsoft modifes their error desription soon.

SUMMARY

helvetica Avant Garde futura frutiger helvetica neue Calibri univers arial Futura Md BT eurostile MyriadPro myriad avenir helveticaneue Trade Gothic zurich ITC Avant Garde optima swiss 721 bauhaus Gill Sans MT candara Tw Cen MT gill sans franklin gothic garamond futura Lt rockwell american typewriter DIN Helvetica bold gotham arial narrow avantgarde officina swiss cambria times Lucida eras Swis721 Berlin Sans FB Demi Bodoni Benguiat Square721 clarendon bahamas corbel stone sans Bodoni MT segoe baskerville souvenir rotis Square 721 trajan humanist SWITZERLAND Helvetica LT copperplate sabon arabic standard 07_53 times new roman helvetica condensed berkeley meta CASLON bembo serpentine courier minion century gothic Arial Black palatino MISTRAL didot avant arial rounded kabel century TheSans goudy cooper Adobe Garamond peignot COCHIN script swis pristina albertus centaur arial tur snell memphis english bookman swis721 bt

Applies To: System Center Data Protection Manager 2010

In DPM, a replica is a complete copy of the protected data on a single volume, database, or storage group. The DPM protection agent on the protected computer sends the data selected for protection to the DPM server. A replica of each member in the protection group is created. Replica creation is one of the more resource-intensive DPM operations, with its greatest impact being on network resources.

Typically, the performance of the replica creation will be limited by the speed of the network connection between the DPM server and the protected computers. That is, the amount of time that it takes to transfer a 1-gigabyte (GB) volume from a protected computer to the DPM server will be determined by the amount of data per second that the network can transmit.

The following table shows the amount of time it would take, at different network speeds, to transmit various amounts of data under optimal conditions. Times are given in hours, except where specified as minutes.

Time Required to Transmit Data over a Network at Various Speeds

 

 

Note

In the preceding table, Gbps = gigabits per second, Mbps = megabits per second, and Kbps = kilobits per second. The figures for a network speed of 1 Gbps assume that the disk speed on the DPM server and the protected computer are not a bottleneck. Typically, the time to complete initial replica (IR) creation can be calculated as follows: IR: hours = ((data size in MB) / (.8 x network speed in MB/s)) / 3600 Note 1: Convert network speed from bits to bytes by dividing by 8. Note 2: The network speed is multiplied by .8 because the maximum network efficiency is approximately 80%.

On an extremely fast network, such as a gigabit connection, the speed of replica creation will be determined by the disk speed of the DPM server or that of the protected computer, whichever is slower.

The impact of replica creation on network performance can be reduced by using network bandwidth usage throttling. For more information, see Using Network Bandwidth Usage Throttling.

To avoid the network load of replica creation, you can create replicas manually from tape or other removable media when creating the initial replica, which can take from hours to days depending on the amount of data to protect. For more information, see Creating Replicas Manually.

If the network goes down during synchronization, DPM will attempt to continue the synchronization from the point where it left off last. If the network goes down during consistency check, DPM will attempt to continue the check if the network comes back up in five minutes. However, if the network remains down for longer than 5 minutes the replica is marked as Inconsistent.

Symptoms

The following error message appears in the event log:

Event ID: 7000
User: N/A
Source: Service Control Manager
Description: The DS1410D service failed to start due to the following error: The system cannot find the file specified.

Cause

The DS1410D service is used by the parallel port adapter. If the server does not have a parallel port it will fail to find the specified device.

Resolution

Caution! This fix requires you to edit the registry. Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

1. Delete/rename the following files: DS1410D.SYS and IB10E32.DLL. This will disable any parallel port operation.

2. Backup and remove the DS1410D registry key located under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services.

This will disable the operating system trying to load the DS1410D.SYS driver at start up.

3. Restart (for the current driver and service to be unloaded from memory).

Problem
When installing a SQL Server cluster, Services Packs, Hotfixes, etc.. there may be a need to reboot both the nodes for changes to take affect and to reboot the server we have to login to each node which is time consuming. Also, there may be a time when you are not able to login to the server after a reboot due to the server being hung. In this tip we will take a look at the SHUTDOWN command and how it could be used.

Solution
This article will guide you through how to use the DOS SHUTDOWN command in Windows to remotely shutdown, restart or log off the local or network computer..

Shutdown command is useful for these scenarios:
1. In case we have to restart multiple computers
2. Server is pingable, but not allowing user to login, in that case we can restart the server remotely
3. User is able to login, but can see only a blue screen, so at that time we can remotely restart the computer

Permission
You must have administrative access to the local or network computer to restart it remotely. For multiple computers in the domain it is recommended to use the Domain Administrator account. 

Command Syntax
Usage: shutdown [-i | -l | -s | -r | -a] [-f] [-m \\computername] [-t xx] [-c "comment"] [-d up:xx:yy]

-i

Show the graphical user interface of shutdown window

-l

To log off from the machine. Make sure that you are not using –l switch with –m switch

-s

Shutdown the desired computer

-r

Shutdown and restart the computer

-a

Abort a system shutdown

-m

-m\\machine name is used for to shutdown/restart/abort remote computer

-f

Forces running application to close without warning

-t

-t xx set timeout for shutdown command to xx seconds

-c

-c”comment” to add shutdown comment, you can add up to max 127 characters

You can also see above output by executing shutdown \? command from DOS 

SHUTDOWN command using GUI
Go to -> Run -- Cmd -- type the shutdown –I command

Here you can select the different options (Restart/Shutdown/Log Off) as per your need. Click on Add… button to add the remote server name.

Execute SHUTDOWN command using command prompt

Here I am restarting remote server (MSSSQLBOX) from the command prompt
shutdown –m \\mssqlbox –r
If you get an access denied/permission error, use the NET USE command
net use \\machine /USER:
shutdown -r -f -m \\machine name

Next Steps

• Take some time to lear about the different switches
• Create a batch file by adding a number of servers with the SHUTDOWN command
• Execute shutdown command by using the time (-s,-t) and immediately execute the abort (-a) command

Description

Problem

Sometimes, you need to know what the security identifier (SID) is for a specific user on the system. To see what the SID is for a specific user, perform the steps below. 

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

1. Open Registry Editor and navigate to:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion \ProfileList
2. Under the ProfileList key, you will see the SIDs. By selecting each one individually, you can look at the value entry and see what user name is associated with that particular SID.

or you can create a .vbs script that looks like this and edit the username and domain fields

strComputer = "."

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")

Set objAccount = objWMIService.Get ("Win32_UserAccount.Name='USERNAME',Domain='DOMAIN'")

Wscript.Echo objAccount.SID

ComboFix allows the manual removal of spyware infections . It 's a specialized effective cleaning tool, which is useful compared to other malware and spyware removers.
After Combofix finished,a report will be created. You can use this report to search and remove infections which are not automatically removed.

How to use combofix:

Disable or Close all anti-spyware, anti-malware antivirus real-time protection, which may affect ComboFix.
Download  (Download)  the latest official version of ComboFix (2.8mb) save to you desktop
Close all programs of you computer
Double click ComboFix.exe on you desktop
When Combofix finished, it will create logs for you.

More Malware Removal Tool : Malwarebytes ' Anti-Malware , Spybot , hijackthis Version 2.0.3 (Beta) , SuperAntiSpyware , Articles

Backup Exec 12.0 for Windows Servers: Backup of the system partition on a Windows 2003 Server may complete with an exception that the NTUser.dat file is skipped.
Error

Completed status: Completed with exceptions
Solution

When the backup of the system drive (the C: partition by default) of a Windows 2003 system runs, the NTUser.dat file may be skipped and the backup job will complete with exceptions. When this behavior occurs, the user's personalized desktop and settings will not exist when the C: partition is restored.

How to determine if affected:

Backup Exec 12.0 for Windows Servers is installed.
Backups of Windows 2003 Server(s) are being performed.
The Advanced Open File Option (AOFO) is not selected for backups of the Windows 2003 system(s).

The installed version of Backup Exec can be verified by opening the interface and choosing About Backup Exec from the Help menu.

Permanent resolution:

This issue has been permanently resolved by Backup Exec for Windows Servers 12.0 Hotfix 303865.
 http://support.veritas.com/docs/303865

Workaround:

Until the fix mentioned in this article can be installed, select the option Use Advanced Open File Option when backing up Windows 2003 systems.
It is found in the Backup Job Properties> Settings> Advanced Open File tab: (Figure 1)

Figure 1

Volume Shadow Copy Service error: A critical component required by the Volume Shadow Copy service is not registered. This might happened if an error occurred during Windows setup or during installation of a Shadow Copy provider. The error returned from CoCreateInstance on class with CLSID {5fc845eb-f299-40f0-9725-34045f7ea8ba} and Name HWPRV is [0x80004002, No such interface supported 

Cause: This error is caused by faulty Acronis software.

Symptoms: Barracuda Backup would not back anything up and the software was not able or very slow to back up locked files and appeared to be 'stuck'. The Event Viewer (Control Panel -> Administrative Tools -> View Event Logs) contained the message above. Specifically look for the text: HWPRV and 5fc845eb-f299-40f0-9725-34045f7ea8ba in the Event View messages.

Another symptom is a very long VSS snapshot generation time.

This error is caused by faulty Acronis software. If you currently use Acronis or have recently uninstalled Acronis and now have problems with other backup programs, follow the steps outlined below.

Resolution:

Step 1: Open the Registry Editor (Start -> Run -> enter "regedit", hit enter)

Step 2: Navigate to the entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSS\Providers

Step 3: (optional) Right-click on the entry {5fc845eb-f299-40f0-9725-34045f7ea8ba} or {f5dbcc43-b847-494e-8083-f030501da611} and export it to a file so you have a backup of it, just in case. You can confirm it's Acronis by opening it up and checking the provider name. It points to a DLL called snapapi.dll (or similar name)

Step 4: Delete the tree {5fc845eb-f299-40f0-9725-34045f7ea8ba} or {f5dbcc43-b847-494e-8083-f030501da611}

Step 5: (optional but recommended): Open the Command Prompt with administrator rights (Start -> All programs -> Accessories -> Right click on Command Prompt and select Run as Administrator) and enter: vssadmin delete shadows /all  to clean up any dead VSS snapshots that may be slowing down your machine

The other day I kept getting a red ! over my Microsoft Office Communicator 2007 R2 icon. I was the only one in the office that was having the problem. Through all off my Googleing I couldnt find a solution, so I decided to check for Windows Updates. There was one Communicator update, Update for Office Communicator 2007 R2 (KB 978564). I installed it, rebooted and was back in business.

First of all you need to install the DPM agent on the machine you want to protect. I got the agent installer from the Agents folder on the DPM 2010 install media and just ran the relevant architecture executable, in my case DPMAgentInstaller_x64.exe. You do not need to anything to install this agent, just double click the EXE and wait for the message to tell you that the agent was installed successfully. You then might need to reboot.

Once the agent is installed it needs to be configured. This is done using SetDPMServer.exe which is located here, <installation drive>\Program Files\Microsoft Data Protection Manager\DPM\bin. Run SetDPMServer.exe with following arguments, you need to specify the DPM server name and a user name for a new local account to be created.

SetDPMServer.exe -DPMServerName <DPMServerName> -IsNonDomainServer -UserName <NewUserName>

You will be prompted to give a password for the new user account and to confirm it, once done the agent is configured and the relevant changes have been made to the Windows firewall.

Now the agent needs to be attached to the DPM server. Attaching DPM agents to a DPM server is much simpler now as it can be done through the DPM GUI as I posted about previously (http://www.clevelandcg.com/kb/microsoft/dpm-2010-attach-manually-installed-agents). To attach a non-domain server agent simply open the DPM console and select the Management pane, click Install... from the Actions menu. When the Protection Agent Installation Wizard opens, select Attach agents and Computer in workgroup or untrusted domain.

Then enter the name of the untrusted computer that the DPM agent is installed on and the user name and password specified when running SetDPMServer.exe. Click "Add >" to add the computer to the selected computers list.

Then simply click Attach !

You should then receive a summary window advising that it attached successfully and that's it, done! With the agent attached you can create a protection group to protect the data on the machine in the usual manner.