A little something about everything

This can be caused if you've changed your administrative account user to improve security on a server.

In order to resolve this issue you will need to stop the max view services in this order:

Then edit cimserver_planned.conf in your maxview storage manager, default path is:

C:\Program Files\Adaptec\maxView Storage Manager\pegasus\cimserver_planned.conf

open with text editor and alter the line from

enableAuthentication=true

to

enableAuthentication=false

It may look something like this: 

save and exit the conf file.

Now start the maxview Storage Manager services in this order:

Now you can login with your admin account correctly.

You've just received notice that your Active Directory server is being used as part of a wide scale dDoS attack. Here is how you can fix it.

Go to the firewall settings on the active directory server or reported server IP and look for the following rules.

• Active Directory Domain Controller - LDAP (TCP-In)
• Active Directory Domain Controller - LDAP (UDP-In)
• Active Directory Domain Controller - LDAP for Global Catalog (TCP-In)
• Active Directory Domain Controller - Secure LDAP (TCP-In)
• Active Directory Domain Controller - Secure LDAP for Global Catalog (TCP-In)

For each of these alter the rule by choosing the Scope tab and entering only IP addresses that should have access to LDAP information. For example, Microsoft Exchange Servers within your network that need access to LDAP.

For assistance securing your network or if you are looking for hosted exchange services check out Area51.mn.

Create and install a certificate using IIS or import a pfx file, the cert can be SHA256 or whatever you want.

Open your Cert Manager,

• Run/open "MMC"
• File, Add/Remove Snap-in, Certificates, OK
• Expand the folder with your cert (generally Personal, Certificates)
• Right Click the Certificate, Open
• Details tab, near the bottom choose thumbprint and select the HASH VALUE
• remove the spaces from the HASHVALUE
• open a Command Prompt with elevated privileges
• run the following command using your SSL cert's thumbprint hash value in place of "HASHVALUE" remove the quotes.
• wmic /namespace:\\root\cimv2\TerminalServices PATH Win32_TSGeneralSetting Set SSLCertificateSHA1Hash="HASHVALUE"
• It should say "Updating property(s) of ...
• then it should say .. update successful

That's it, you're done.

Many times you may receive emails in Outlook that are pretending to be someone they are not, even sometimes they may appear to be coming from yourself.

Simple and effective way to see who the sender of each email really is,

1. Click on the window where you view incoming emails, then click "view", "add columns"
2. Now click "New Column" and name it something like "Sender"
3. Change the Type to "Formula", click "edit" and enter the following: 
   right(([SearchFromEmail],[SearchFromEmail]),InStr(1,[SearchFromEmail],"@")) or right([SearchFromEmail],len([SearchFromEmail])-InStr(1,[SearchFromEmail],"@")) to show just the domain.

The most effective method will be to use the global.asax file, here is a basic example:

<script language="C#" runat="server">
protected void Application_BeginRequest(Object sender, EventArgs e)	{
if (HttpContext.Current.Request.Url.ToString().ToLower().Contains("http://"))
{
    HttpContext.Current.Response.Status = "301 Moved Permanently"; 
    HttpContext.Current.Response.AddHeader("Location", Request.Url.ToString().ToLower().Replace("http://","https://")); 
}
}
</script>

In some cases you may already have an application using the global.asax file, you can in many cases add the _BeginRequest function or adapt it if it already exists. For example add this after the <script runat="server"> tag but before any other code.

protected void Application_BeginRequest(object sender, EventArgs e)	{
	if (HttpContext.Current.Request.Url.ToString().ToLower().Contains("http://"))	{
	HttpContext.Current.Response.Status = "301 Moved Permanently"; 
	HttpContext.Current.Response.AddHeader("Location", Request.Url.ToString().ToLower().Replace("http://","https://")); 
	}

In some cases this will throw and error, before sure to check the rest of the global.asax file for any other begin requests that may be conflicting. In some cases you may need to adapt the code to work in parallel with exiting code.