Tag: Microsoft | IT Nota

How to Set MS Edge for IE Compatibility Mode

If you need to access legacy websites designed for earlier versions of Internet Explorer, such as those using VBScript client (as opposed to JavaScript), you may encounter issues with the website rendering or functionality in modern browsers, including Microsoft Edge.

However, there is a solution in Microsoft Edge that can help resolve these issues. By using Internet Explorer compatibility mode, you can ensure that these legacy websites will display and function properly in Microsoft Edge.

Here are the steps to set Microsoft Edge to Internet Explorer compatibility mode:

Method 1

Open Microsoft Edge and click on the three dots (…) in the upper-right corner to access the settings menu.
Select the Settings option from the drop-down menu.
Under Settings on the left pane, scroll down to the Default browser section.
Click on the Add button under Internet Explorer mode pages and an Add a page window will open.
Enter the full URL (or IP address) of the legacy site and click the Add button, it will bring you back to the Settings window with the newly added site.
Close the Settings page and restart Microsoft Edge.

Here’s a summary of the steps in a screenshot:

After restarting Microsoft Edge, it will be set to use Internet Explorer compatibility mode and you should be able to access websites and web applications that require Internet Explorer.

Method 2

If you have Enterprise Mode turned on, you can just add the website URL to the file sites.xml:

Go to C:\IEEnterpriseMode folder and look for a file called sites.xml.

Open sites.xml with a text editor and you should see something similar to this:

<site-list version="1">
  <created-by>
    <tool>EMIESiteListManager</tool>
    <version>12.0.0.0</version>
    <date-created>01/01/2023 00:24:49</date-created>
  </created-by>
  <site url="www.itnota.com">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
</site-list>

Just add all the sites you want to access with IE compatibility mode to the XML file like so:

<site-list version="1">
  <created-by>
    <tool>EMIESiteListManager</tool>
    <version>12.0.0.0</version>
    <date-created>01/01/2023 00:24:49</date-created>
  </created-by>
  <site url="www.itnota.com">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
  <site url="www.mysite.com">
    <compat-mode>IE11</compat-mode>
    <open-in>IE11</open-in>
  </site>
</site-list>

Once completed, just save the file and exit.

You can try each method or both in conjunction. It shouldn’t affect one or the other. That’s all there is to it.

SSIS Best Practice with Naming Conventions

In 2006, Jamie Thomson originally came up with naming conventions for SSIS tasks and data flow components which makes packages and logs more readable and easier to find.

Koen Verbeeck and André Kamman extended the existing list with almost 40 tasks/components since then.

This list should be used just as a reference if you want to use standard naming convention in SSIS.

The point is whether or not you want to follow this naming standard, it’s always better to use a standard for your package maintainability and readibility.

Task

The acronyms below can be used at the beginning of the names of tasks to identify what type of task it is.

Task	Prefix
For Loop Container	FLC
Foreach Loop Container	FELC
Sequence Container	SEQC
ActiveX Script	AXS
Analysis Services Execute DDL	ASE
Analysis Services Processing	ASP
Azure Blob Download	ADT
Azure Blob Upload	AUT
Azure HDInsight Create Cluster	ACCT
Azure HDInsight Delete Cluster	ACDT
Azure HDInsight Hive	AHT
Azure HDInsight Pig	APT
Back Up Database	BACKUP
Bulk Insert	BLK
CDC Control	CDC
Check Database Integrity	CHECKDB
Data Flow	DFT
Data Mining Query	DMQ
Data Profiling	DPT
Execute DTS 2000 Package	EDPT
Execute Package	EPT
Execute Process	EPR
Execute SQL Server Agent Job	AGENT
Execute SQL	SQL
Execute T-SQL Statement	TSQL
File System	FSYS
FTP	FTP
Hadoop File System	HFSYS
Hadoop Hive	HIVE
Hadoop Pig	PIG
History Cleanup	HISTCT
Maintenance Cleanup	MAINCT
Message Queue	MSMQ
Notify Operator	NOT
Rebuild Index	REBIT
Reorganize Index	REOIT
Script	SCR
Send Mail	SMT
Shrink Database	SHRINKDB
Transfer Database	TDB
Transfer Error Messages	TEM
Transfer Jobs	TJT
Transfer Logins	TLT
Transfer Master Stored Procedures	TSP
Transfer SQL Server Objects	TSO
Update Statistics	STAT
Web Service	WST
WMI Data Reader	WMID
WMI Event Watcher	WMIE
XML	XML
Expression	EXPR

Components

These acronyms should be used at the beginning of the names of components to identify what type of component it is.

Component	Prefix
ADO NET Source	ADO_SRC
Azure Blob Source	AB_SRC
CDC Source	CDC_SRC
DataReader Source	DR_SRC
Excel Source	EX_SRC
Flat File Source	FF_SRC
HDFS File Source	HDFS_SRC
OData Source	ODATA_SRC
ODBC Source	ODBC_SRC
OLE DB Source	OLE_SRC
Raw File Source	RF_SRC
XML Source	XML_SRC
Aggregate	AGG
Audit	AUD
Balanced Data Distributor	BDD
Cache Transform	CCH
CDC Splitter	CDCS
Character Map	CHM
Conditional Split	CSPL
Copy Column	CPYC
Data Conversion	DCNV
Data Mining Query	DMQ
Derived Column	DER
DQS Cleansing	DQSC
Export Column	EXPC
Fuzzy Grouping	FZG
Fuzzy Lookup	FZL
Import Column	IMPC
Lookup	LKP
Merge	MRG
Merge Join	MRGJ
Multicast	MLT
OLE DB Command	CMD
Percentage Sampling	PSMP
Pivot	PVT
Row Count	CNT
Row Sampling	RSMP
Script Component	SCR
Slowly Changing Dimension	SCD
Sort	SRT
Term Extraction	TEX
Term Lookup	TEL
Union All	ALL
Unpivot	UPVT
ADO NET Destination	ADO_DST
Azure Blob Destination	AB_DST
Data Mining Model Training	DMMT_DST
Data Streaming Destination	DS_DST
DataReader Destination	DR_DST
Dimension Processing	DP_DST
Excel Destination	EX_DST
Flat File Destination	FF_DST
HDFS File Destination	HDFS_DST
ODBC Destination	ODBC_DST
OLE DB Destination	OLE_DST
Partition Processing	PP_DST
Raw File Destination	RF_DST
Recordset Destination	RS_DST
SharePoint List Destination	SPL_DST
SQL Server Compact Destination	SSC_DST
SQL Server Destination	SS_DST
SQL Server Mobile Destination	SSM_DST

How to Install a Certificate on Windows Server

Steps to Install a Certificate on a Window Server

Right-click on Windows button at the bottom left corner and select Run.
Type in mmc and click OK.
On the new Console window menu, click on file and select Add/Remove Snap-in… or press Ctrl+M.
Select Certificates and click on Add > button. Select Computer account and click Next.
Click on Local computer and click Finish. You should see Certificates (Local Computer) on the Selected snap-ins: pane. click OK.
Under the Console Root on the left pane, expand on Personal, Certificates.
Import the certificate (pfx file) from Local Machine and click Next.
Select the certificate file from the local folder and click Next.
Type in the password for the certificate and check on Include all extended properties and click Next.
Check on Place all certificates in the following store – Certificate store: and type in Personal if it’s not already filled in. Click Next.
The Certificate Import Wizard will confirm all the selection. If everything is correct, just click on Finish and you should get a confirmation that the import was successful. Click OK and you’re done.

Please keep in mind if you’re installing this certificate for a website on IIS, you still need to assign the certificate to the corresponding website on IIS.

How to Serve AVIF Image on IIS

How do you take advantage of serving AVIF image from IIS server? For simplicity sake, since the setup is very similar to serving WebP format, I’m going to use the same screenshot illustrations from that post.

The problem with using IIS Server is by default IIS does not recognize AVIF as an image type so it cannot correctly render it on the page even if the browser can support it.

Using a test page avif-test.html with the content below, the page will render as shown.

<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>IT Nota AVIF Test Render</title>
</head>
<body>
  <h1>PNG</h1>
  <img src="images/caniuse-AVIF-Test.png" width="368" height="335" alt="PNG" />

  <h1>AVIF</h1>
  <img src="images/caniuse-AVIF-Test.avif" width="368" height="335" alt="AVIF" />
</body>
</html>

The screenshot above is taken from a webp test page, however the experience will be very similar for AVIF.

The issue stems from the fact that IIS does not recognize AVIF as a legitimate MIME type. So with a simple fix, we can make IIS to treat the new format as a valid image file.

How to Enable AVIF on IIS

Launch IIS Manager.
Click on your main server on the left pane to make sure we’re making the change on a server level (as opposed to a site level). Then click on the MIME Types.
On the right pane of MIME Types dialog box, click on Add… link.
We want to add a new MIME type of AVIF as an image type so IIS knows how to handle this new format.
In Add MIME Type box, enter .avif as the file name extension and image/avif as the MIME type and click OK.

That’s all there is to it.

Now if you reload your Chrome browser, you should be able to see both image files rendered correctly.

The screenshot above is taken from a webp test page, however the experience will be very similar for AVIF.

As a side note, currently, the way to compress the image to AVIF is to do it from avif.io website.

How to Force HTTPS in IIS

This is a short tutorial on how to force an HTTPS connection to your website in IIS. The way we do it is by adding a URL Rewrite rule that will redirect any unsecured incoming traffic to HTTPS.

Steps

The first step you need to check is if you have URL Rewrite module installed. If you don’t have it installed, you can download it from the link at the bottom of this post.
You can either use the GUI on IIS to set this up, or apply the rules in web.config file of your website. You just need to substitue the target URL with your own.

Open your web.config in a text editor and add the rewrite rule inside the system.webServer child element:

<system.webServer>
  <rewrite>
    <rules>
      <rule name="Force HTTPS" enabled="true" stopProcessing="true">
        <match url="(.*)" />
        <action type="Redirect" url="https://www.itnota.com" />
        <conditions logicalGrouping="MatchAll">
          <add input="{HTTPS}" pattern="^OFF$" />
        </conditions>
      </rule>
    </rules>
  </rewrite>
</system.webServer>

Or if you use IIS GUI, it should look something similar to this:

IIS Rules using URL Rewrite to force HTTPS connection

That’s all there is to force HTTPS connection to your website. In this day and age, this should be the minimum setup for any websites.

Download

URL Rewrite

How to Set MS Edge for IE Compatibility Mode

Method 1

Method 2

Further Reading

SSIS Best Practice with Naming Conventions

Task

Components

Further Reading

How to Install a Certificate on Windows Server

Steps to Install a Certificate on a Window Server

Further Reading

How to Serve AVIF Image on IIS

How to Enable AVIF on IIS

Further Reading

How to Force HTTPS in IIS

Steps

Download

Recent Posts

Method 1

Method 2

Further Reading

Task

Components

Further Reading

Steps to Install a Certificate on a Window Server

Further Reading

How to Enable AVIF on IIS

Further Reading

Steps

Download

Recent Posts

Tags