How do I open it .emz files?

Regarding .EMZ files, they're images.  You can import them to a MS word document via Insert->Picture.

XStandard Zip

Overview

The Zip component provides industry-standard Zip archive functionality. It is designed to be easy to use. You can pack/unpack a file or folder with a single line of code. If you need to create or extract Zip files on the fly, this component is for you. This component can be used in environments that support COM such as Active Server Pages, Windows Scripting Host, Visual Basic, etc.

License
    Freeware
Type
    32-bit ActiveX DLL
Version
    2.5
File Name
    XZip.dll
Download Package
    x-zip.zip

Download

Download Zip Component

Visual C++ users can download header files.
Installation Instructions

    Move the dll to a directory like: C:\Program Files\XStandard\Bin\.
    Open a command prompt and cd to the directory where the dll is located.
    Type regsvr32 XZip.dll or on 64-bit OS type C:\Windows\SysWOW64\regsvr32.exe XZip.dll
    Grant "Read & Execute" file permissions on this dll to Everyone.

Note, the command prompt must be "Run as administrator" as shown in the screen shot below.

Context menu for the command prompt showing the option to run as administrator.
Uninstall Instructions

    Open a command prompt and cd to the directory where the dll is located.
    Type regsvr32 -u XZip.dll or on 64-bit OS type C:\Windows\SysWOW64\regsvr32.exe -u XZip.dll

Usage from 64-bit OS

Please see instructions for 64-bit OS usage.

Persits.MailSender 'Access is denied'

If you happen to be using the Persits mail component and you get the 'Access is denied' exception:
Persits.MailSender.4 error '800a0011'
Access is denied.
/pages/somepage.asp, line 208
You'll probably find, from the Persits support site or elsewhere, that the queue folder needs to have increased permissions. It doesn't however tell you where this is. So here is the default install path for version 4:
C:\Program Files\Persits Software\AspEmail\Queue
As far as the permissions go I have found that granting Read and Write permissions to the accessing account on that folder is sufficient. In IIS 6 the accessing account for .NET will be the identity of the App Pool assigned to the site (if you are not doing impersonation) which is the NetworkService account by default. For Classic ASP it will be the anon account (Which by default is the IUSR_xxx) for anon access or the user/group if you are doing other types of auth.

Exporting and Importing Sites and App Pools from IIS 7 and 7.5

When using multiple IIS server in a Load Balanced Environment it will  be alot of work to create all your website twice with the same settings on each webserver. Therefor it is possible to export and import your configuration from one webserver to the other. This will also be usefull when your upgrading from IIS 7 (Windows Server 2008) to IIS 7.5 (Windows Server 2008 R2).
When you create a website in IIS 7 or 7.5 a unique application pool will also be created and used by this website, that’s why you need to import these application pools first on the second webserver before importing the website(s).
To Export the Application Pools on IIS 7 :
%windir%\system32\inetsrv\appcmd list apppool /config /xml > c:\apppools.xml
This will export all the application pools on your webserver, therefor you need to edit the apppools.xml and remove the application that you do not need to import for example:

• DefaultAppPool
• Classic .NET AppPool
• SecurityTokenServiceApplicationPool

And other apppools that already exist on the second webserver, appcmd doesn’t skip already existing apppools, it just quit’s and doesn’t import any.
To import the Application Pools:
%windir%\system32\inetsrv\appcmd add apppool /in < c:\apppools.xml
All the AppPools in the xml will be created on your second webserver.
To Export all your website:
%windir%\system32\inetsrv\appcmd list site /config /xml > c:\sites.xml
This will export all the websites on your webserver, therefor you need to edit the sites.xml and remove the websites that you do not need to import for example:

• Default Website

And all other websites that already exist on the second webserver.
To Import the website:
%windir%\system32\inetsrv\appcmd add site /in < c:\sites.xml
It’s also possible to export a single website or application pool all you need to do is add the name of the Application Pool or Website to the command line:
To export/import a single application pool:
%windir%\system32\inetsrv\appcmd list apppool “MyAppPool” /config /xml > c:\myapppool.xml
Import:
%windir%\system32\inetsrv\appcmd add apppool /in < c:\myapppool.xml
To export/import a single website:
%windir%\system32\inetsrv\appcmd list site “MyWebsite” /config /xml > c:\mywebsite.xml
Import:
%windir%\system32\inetsrv\appcmd add site /in < c:\mywebsite.xml

VBA macro language support

1. Run the Office Setup program again.
   1.  Quit all programs.
   2.  Double-click the Add/Remove Programs icon in the Microsoft Windows Control Panel.
   3.  Do one of the following:
   If you installed your Office program as part of Microsoft Office, click Microsoft Office in the Currently installed programs box, and then click the Change button.
   If you installed your Office program individually, click the name of your program in the Currently installed programs box, and then click the Change button.
2. On the Features to install screen in the Setup program, click the plus sign (+) next to Office Shared Features.
3. Select Visual Basic for Applications, click the arrow next to your selection, and then click Run from My Computer.

Enable Network Level Authentication for Remote Desktop

Enabling Network Level Authentication on Windows XP Service Pack 3 for access to Server 2008+ via Remote Desktop

The remote computer requires Network Level Authentication, which your computer does not support.

To enable NLA in XP machines; first install XP SP3, then edit the registry settings on the XP client machine to allow NLA

• Configure Network Level Authentication

1. Click Start, click Run, type regedit, and then press ENTER.
2. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
5. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
8. Exit Registry Editor.
9. Restart the computer.

Directory you want to print the contents

Windows command line and MS-DOS users

1. Get to the MS-DOS prompt or the Windows command line.
2. Navigate to the directory containing the content you'd like a list to print. If you're new to the command line, familiarize yourself with the cd command and the dir command.
3. Once in the directory you want to print the contents of, type one of the below commands.

dir > print.txt

The above command takes a list of all the files and all of the information about the files, including size, modified date, etc., and sends that output to the print.txt file in the current directory.

dir /b > print.txt

The above command would print only the file names and not the file information of the files in the current directory.

dir /s /b > print.txt

The above command would print only the file names of the files in the current directory and any other files in the sub-directories within the current directory.

4. After executing any of the above commands, the print.txt file is created. Open this file in any text editor (e.g. Notepad) and print the file. You can also print from the command prompt by typing notepad print.txt.

Block Skype connections

There is a popular belief that Skype client is very hard to block on the network layer, due to it’s Peer-To-Peer behavior and usage of HTTP/S ports.

However at present time (December, 2012) Skype client connections can be blocked pretty simply by a few firewall rules.
After startup, Skype client receives a number of it’s master (login?) servers – dsnX.d.skype.net. Currently there are 16 DNS entries from dsn0.d.skype.net to dsn16.dsn.skype.net.
Using simple bash script (uses Linux DNS utility – dig) we can get most of these server’s IP addresses:

Just block all access to following networks and Skype client won’t be able to authenticate and connect.
111.221.74.0/24
111.221.77.0/24
157.55.130.0/24
157.55.235.0/24
157.55.56.0/24
157.56.52.0/24
213.199.179.0/24
64.4.23.0/24
65.55.223.0/24
For Linux router, with IPtables firewall, you may use following command:

for ip in 111.221.74.0/24 111.221.77.0/24 157.55.130.0/24 157.55.235.0/24 157.55.56.0/24 157.56.52.0/24 213.199.179.0/24 64.4.23.0/24 65.55.223.0/24; do iptables -A OUTPUT -d $ip -j DROP; done

How to Open Blocked Files in Office 2013

By Ajeet Yadav

If you have upgraded to Office 2013, or Office 365, you may have run into problems opening files that have been emailed to you. Try to open a Word file you have received as an email attachment and you are likely to find that Word not only refuses to open the files, but fails to provide much in the way of help.
The reason the file cannot be opened is that it originated from a different computer, and for this very reason it is seen as a potential threat by Office. When you are dealing with files that have been emailed to you, or you have downloaded from the internet, this makes a degree of sense from a security point of view, but it is also extremely annoying.

The problem is exacerbated by the fact that files stored on a network drive or copied from other computers on your home network can also be affected if they have been archived. The absence of any helpful pointers to how you should go about opening the file in question could leave you pulling out your hair, but there are a couple of solutions.
Office 2013 employs a similar technique to Internet Explorer to determine where files originated from, and this can lead to security issues.

Unblock Individual Files

This may be an issue that you don’t encounter all that often, so the best plan of attack to start with is to unblock files on an individual basis.
Right-click a file that has been block by Office and select Properties from the context menu. On the General tab, click the Unblock button at the bottom of the dialog and then click OK. The next time you double-click the file it will open as you would expect.

Unblocking All Files

If you find that you are frequently encountering this error message, you may want to take a different approach. I store all of my writing in zip files on a network drive and I have found that any file contained within an archive that I try to access is automatically blocked – the number of times I have to access these files means I’m not happy to have to unblock each file one after another.
In Word 2013 – or whichever Office application you are having problems with – click the File menu and select Options. Click the Trust Center link to the left.

Click the Trust Center Settings button and then click the Trusted Locations link to the left. Here you can specify folders that should always be trusted so that the file stored in them can always be opened.
If you are struggling to open files stored on a network drive you can add this to your list of trusted location; click the ‘Add new location’ button

Click Browse and then navigate to the folder or drive you would like to unblock. You also have the option of ticking the ‘Subfolders of this location are also trusted’ to ensure that all files from this drive can be opened.

If you click OK followed by OK and then attempt to re-open a file that has been blocked, you will find that it opens without issues.
This solution does not help entirely however. It is not possible to use this method to unblock network locations – it does mean, however, that you can copy troublesome files from a network location to a designated ‘safe’ folder so they can be opened from there.

Disable Security

There is another option available to you, but it is one that should be used with caution. Files from potentially unsafe locations are blocked for that very reason – there is a possibility that they are dangerous. But if you are determined to be able to open whichever files you want, you can bypass this security.
In the Trust Center, head to the Protected View section and untick the boxes labeled ‘Enable Protected View for files originating from the Internet’ and ‘Enable Protected View for files located in potential unsafe locations’ before clicking OK

Use IPSec for Filtering Ports and Authentication

How To: Use IPSec for Filtering Ports and Authentication

 

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Improving Web Application Security: Threats and Countermeasures J.D. Meier, Alex Mackman, Michael Dunner, Srinath Vasireddy, Ray Escamilla and Anandha Murukan
Microsoft Corporation
Published: June 2003
Last Revised: January 2006

Applies to:

• Microsoft Windows® 2000 operating system

See the "patterns & practices Security Guidance for Applications Index" for links to additional security resources.
See the Landing Page for the starting point and a complete overview of Improving Web Application Security: Threats and Countermeasures.
Summary: Internet Protocol security (IPSec) is a protocol, not a service, that provides encryption, integrity, and authentication services for IP-based network traffic. Because IPSec provides server-to-server protection, you can use IPSec to counter internal threats to the network, including eavesdropping, tampering, man in the middle attacks, IP spoofing, and other password-based attacks. IPSec is completely transparent to applications because encryption, integrity, and authentication services are implemented at the transport level. Applications continue to communicate normally with one another using TCP and UDP ports.

Note   This How to is applicable to the Microsoft Windows 2000 operating system. For more information on Internet Protocol security (IPSec) support in Windows Server 2003, see "Internet Protocol Security for Microsoft Windows Server 2003."

Contents

This How To contains the following sections:
What you must know Restricting Web server communication Restricting database server communication Restricting server-to-server communication Using IPSec tools Additional Resources

What You Must Know

Before you start to configure IPSec, you should be aware of the following.

Identify Your Protocol and Port Requirements

Before you create and apply IPSec policies to block ports and protocols, make sure you know which communication you need to secure including the ports and protocols used by day-to-day operations. Consider the protocol and port requirements for remote administration, application communication, and authentication.

IPSec Does Not Secure All Communication

• Several types of IP traffic are exempt from filtering. For more information, see Microsoft Knowledge Base article 253169, Traffic That Can and Cannot Be Secured by IPSec.

Firewalls and IPSec

If a firewall separates two hosts that use IPSec to secure the communication channel, the firewall must open the following ports:

• IP Protocol ID 50 for IPSec Encapsulating Security Protocol (ESP) traffic
• IP Protocol ID 51 for IPSec Authentication Header (AH) traffic
• UDP port 500 for Internet Key Exchange (IKE/ISAKMP) negotiation traffic

Filters, Filter Actions, and Rules

An IPSec policy consists of a set of filters, filter actions, and rules.

• Filters A filter is used to match traffic. It consists of:
  
  • A source IP address or range of addresses
  • A destination IP address or range of addresses
  • An IP protocol, such as TCP, UDP, or "any"
  • Source and destination ports (for TCP or UDP only)

  Note   An IP filter list is used to group multiple filters together so that multiple IP addresses and protocols can be combined into a single filter.

• Filter Actions A filter action specifies which actions to take when a given filter is invoked. It can be one of the following:
  
  • Permit. The traffic is not secured; it is allowed to be sent and received without intervention.
  • Block. The traffic is not permitted.
  • Negotiate security. The endpoints must agree on and then use a secure method to communicate. If they cannot agree on a method, the communication does not take place. If negotiation fails, you can specify whether to allow unsecured communication or to whether all communication should be blocked.
• Rules A rule associates a filter with a filter action and is defined by the IPSec policy.

Restricting Web Server Communication

The following example shows you how to use IPSec to limit communication with a Web server to port 80 (for HTTP traffic) and port 443 (for HTTPS traffic that uses SSL.) This is a common requirement for Internet-facing Web servers.

Note   After applying the steps below, communication will be limited to port 80 and 443. In a real world environment, you will require additional communication such as that required for remote administration, database access and authentication. A complete IPSec policy, in a production environment, will include all authorized communication.

Create filter actions

1. Start the Local Security Policy Microsoft Management Console (MMC) snap-in.
2. Right-click IPSec Security Policies on Local Machine, and then click Manage IP filter lists and filter actions.
3. Click the Manage Filter Actions tab.
4. Click Add to create a new filter action, and then click Next to move past the introductory Wizard dialog box.
5. Type MyPermit as the name for the new filter action. This filter action is used to permit traffic.
6. Click Next.
7. Select Permit, click Next, and then click Finish.
8. Create a second filter action called "MyBlock" by repeating steps 4 to 8. This time, select Block when you are prompted by the Filter Action dialog box.
9. Click Close to close the Manage IP filter lists and filter actions dialog box.

Create IP filters and filter lists

1. Right-click IPSec Security Policies on Local Machine, and then click Manage IP filter lists and filter actions.
2. Click Add to add a new IP filter list., and then type MatchAllTraffic for the filter list name.
3. Click Add to create a new filter and proceed through the IP Filter Wizard dialogs boxes by selecting the default options. This creates a filter that matches all traffic.
4. Click Close to close the IP Filter List dialog box.
5. Click Add to create a new IP filter list, and then type MatchHTTPAndHTTPS for the filter list name.
6. Click Add, and then click Next to move past the introductory Wizard dialog box.
7. Select Any IP Address from the Source address drop-down list, and then click Next.
8. Select My IP Address from the Destination address drop-down list, and then click Next.
9. Select TCP from the Select a protocol type drop-down list, and then click Next.
10. Select To this port and then specify port 80.
11. Click Next and then Finish.
12. Click Add, and then repeat steps 9 to 14 to create another filter that allows traffic through port 443. Use the following values to create a filter that allows TCP over port 443:
    
    • Source Address: Any IP address
    • Destination Address: My IP Address
    • Protocol: TCP
    • From Port: Any
    • To Port: 443

After finishing these steps, your IP Filter List should look like the one that Figure 5 shows.

Figure 5

IP Filter List dialog box
After creating the filter actions and filter lists, you need to create a policy and two rules to associate the filters with the filter actions.

Create and apply IPSec policy

1. In the main window of the Local Security Policy snap-in, right-click IPSec Security policies on Local Machine, and then click Create IPSecurity Policy.
2. Click Next to move past the initial Wizard dialog box.
3. Type MyPolicy for the IPSec policy name and IPSec policy for a Web server that accepts traffic to TCP/80 and TCP/443 from anyone for the description, and then click Next.
4. Clear the Activate the default response rule check box, click Next, and then click Finish. The MyPolicy Properties dialog box is displayed so that you can edit the policy properties.
5. Click Add to start the Security Rule Wizard, and then click Next to move past the introductory dialog box.
6. Select This rule does not specify a tunnel, and then click Next.
7. Select All network connections, and then click Next.
8. Select Windows 2000 default (Kerberos V5 protocol), and then click Next.
9. Select the MatchHTTPAndHTTPS filter list, and then click Next.
10. Select the MyPermit filter action, click Next, and then click Finish.
11. Create a second rule by repeating steps 5 to 10. Instead of selecting MatchHTTPAndHTTPS and MyPermit, select MatchAllTraffic and MyBlock.

After creating the second rule, the MyPolicy Properties dialog box should look like the one in Figure 6.

Figure 6

MyPolicy Properties dialog box
Your IPSec policy is now ready to use. To activate the policy, right-click MyPolicy and then click Assign.

Summary of What You Just Did

In the previous three procedures, you performed these actions:

• You started by creating two filter actions: one to allow traffic and one to block traffic.
• Next, you created two IP filter lists. The one called MatchAllTraffic matches on all traffic, regardless of port. The one called MatchHTTPAndHTTPS contains two filters that match TCP traffic from any source address to TCP ports 80 and 443.
• Then you created an IPSec policy by creating a rule that associated the MyBlock filter action with the MatchAllTraffic filter list and the MyPermit filter action with the MatchHTTPAndHTTPS filter list. The result of this is that the Web server only allows TCP traffic destined for port 80 or 443. All other traffic is rejected.

Restricting Database Server Communication

On a dedicated SQL Server database server, you often want to restrict communication to a specific SQL Server port over a particular protocol. By default, SQL Server listens on TCP port 1433, and UDP port 1434 is used for negotiation purposes.
The following steps restrict a database server so that it only accepts incoming connections on TCP port 1433 and UDP port 1434:

• Create two filter actions: one to permit traffic and the other to block traffic. For details, see the Create filter actions procedure under "Restricting Web Server Communication" earlier in this How To.
• Create two filter lists: one that matches all traffic and one that contains two filters that match TCP traffic destined for port 1433 and UDP traffic destined for port 1433. For details, see "Create IP filter lists and filters" under "Restricting Web Server Communication" earlier in this How To. The required filters are summarized below.
  • Enter the following values to create a filter that allows TCP over port 1433:
  • Source Address: Any IP address
  • Destination Address: My IP Address
  • Protocol: TCP
  • From Port: Any
  • To Port: 1433
  • Enter the following values to create a filter that allows UDP over port 1434:
  • Source Address: Any IP address
  • Destination Address: My IP Address
  • Protocol: UDP
  • From Port: Any
  • To Port: 1434
• Create and apply IPSec policy by repeating the procedure under "Restricting Web Server Communication" earlier in this How To.

Restricting Server-to-Server Communication

You can also use IPSec to provide server authentication. This is useful when restricting the range of computers that can connect to middle-tier application servers or database servers. IPSec provides three authentication options:

• Kerberos To use Kerberos, the computers must:
  
  • Be part of the same domain and forest
  • Be within a specific source address range
  • Be within the same subnet
  • Use static IP addresses
• Pre-shared secret key To use pre-shared secret-key-based authentication, the two computers must share an encryption key.
• Certificate-based authentication To use certificate authentication, the two computers must trust a common certificate authority (CA), and the server that performs the authentication must request and install a certificate from the CA.

In this section, you set up IPSec authentication between two servers by using a pre-shared secret key.

To perform server-to-server authentication

1. Start the Local Security Policy MMC snap-in.
2. Right-click IPSec Security policies on the local machine, and then click Create IP Security Policy.
3. Type "MyAuthPolicy" for the name, and then click Next.
4. Clear the Activate the default response rule check box.
5. Click Next and then Finish. The MyAuthPolicy Properties dialog box is displayed so that you can edit the policy properties.
6. Click Add, and then click Next three times.
7. In the Authentication Method dialog box, select Use this string to protect the key exchange (preshared key).
8. Enter a long, random set of characters in the text box, and then click Next. You should copy the key to a floppy disk or CD. You need it to configure the communicating server.
9. In the IP Filter List dialog box, select All IP Traffic, and then click Next.
10. In the Filter Action dialog box, select Request Security (Optional), and then click Next.
11. Click Finish.
12. Test your application to verify the configured policy.

Using IPSec Tools

This section describes two useful IPSec diagnostic tools that are available as part of the Windows 2000 resource kit:

• Netdiag.exe
• IPSecpol.exe

Netdiag.exe

Before creating a new policy, determine if your system already has an existing policy. You can do this by performing the following steps:

To check for existing IPSec policy

1. To install Netdiag.exe, run the Setup.msi program from the \Support\Tools folder on the Windows 2000 Server CD. The tools are installed in C:\Program Files\Resource kit.
2. Run the following command from the command line:

   netdiag /test:ipsec
   

   If there are no existing filters, then the output looks like the following:
   

   IP Security test . . . . . . . . . : Passed IPSec policy service is active, but no policy is assigned.
   

IPSecpol.exe

The Internet Protocol Security Policies tool helps you automate the creation of policies in local and remote registries. The tool supports the same settings that you can configure by using the MMC snap-in.
Download the tool from the Microsoft Windows 2000 Web site at http://technet.microsoft.com/en-us/windowsserver/2000/default.aspx.
For detailed examples of using Ipsecpol.exe to create and manipulate IPSec rules, see Microsoft Knowledge Base article 813878, "How to Block Specific Network Protocols and Ports by Using IPSec."

Additional Resources

For more information, see the following resources:

• Step-by-Step guide to IPSec at http://technet.microsoft.com/en-us/windowsserver/2000/default.aspx.
• IP Security for Windows 2000 Server at http://technet.microsoft.com/en-us/windowsserver/2000/default.aspx.
• "How To: Use IPSec to Provide Secure Communication Between Two Servers" in the How To section of "Building Secure ASP.NET Applications" on MSDN.
• Article 313190, "How To: Use IPSec IP Filter Lists in Windows 2000" in the Microsoft Knowledge Base.
• Article 813878, "How to Block Specific Network Protocols and Ports by Using IPSec" in the Microsoft Knowledge Base.
• Article 313195, "How To: Use IPSec Monitor in Windows 2000" in the Microsoft Knowledge Base.
• IPSec considerations at http://www.microsoft.com/technet/prodtechnol/winxppro/proddocs/sag_IPSECsec_con.asp.
• IPSec Operations on Windows Server 2003 at http://technet.microsoft.com/en-us/library/cc706993(WS.10).aspx.

How To Configure Legal Notices On Domain Computers Using Group Policy

How To Configure Legal Notices On Domain Computers Using Group Policy – Few years ago when i was working on Windows Server 2008 R2, I was told by my manager to configure a logon banner. What came to my mind was to write a script for it and run the script at logon. There are 2 ways to configure legal notices on domain computers, you can configure it by writing a script and executing it at the logon or configuring legal notice using a group policy. I believe the second method is very easy. You can configure Windows Server to display a message to users when they log on. You can use the message display functionality to personalize the logon process, provide news or information, and for other similar purposes. The message appears after the user presses CTRL+ALT+DEL and disappears after the user clicks OK.
In this post we will see on how to configure legal notices on domain computers using group policy. We will create a group policy, modify the policy settings and link it to the domain. I am configuring this policy on a domain controller running Windows server 2008 R2 SP1 edition.
Login to the domain controller machine with the administrator account. Click on Start, Click on Administrative Tools, Click on Group Policy Management. Under Domains, right click your domain and click on Create a GPO in this domain, and link it here.

We will create a policy named Logon_Banner. Click on OK.


Right the policy Logon_Banner and click on Edit. On Group Policy Management Editor, click on Computer Configuration, expand Policies, expand Windows Setttings, expand Security Settings, expand Local Policies, click on Security Options.

On the right pane look for the policy Interactive Logon : Message text for users attempting to log on. This security setting specifies a text message that is displayed to users when they log on. You can paste the Logon text that is to be displayed to the users before they log in. Click on Apply and OK.

On the right pane look for the policy Interactive Logon : Message title for users attempting to log on. This security setting allows the title to appear in the title bar of the window that contains the Interactive logon.Type the title text and click on Apply and OK.

On the client computer open the command prompt and run the command gpupdate.

Log off from the client computer. Hold CTRL+ALT and press DEL. You must find the logon banner. Click on OK to login to the computer.

Blank SOLIDWORKS Installation Manager Problem Solved

If you experience a blank SOLIDWORKS Installation Manager window while attempting to install your software this may be caused by either your local firewall blocking HTML files from rendering on screen or your Internet Browser settings.

Blank SOLIDWORKS Installation Manager

Solution #1: Unblock HTML

After unzipping the SOLIDWORKS Installation Manager files you downloaded from solidworks.com you may need to unblock HTML files:

1. Browse to the downloaded installation file location  <downloads>\sldim\lang\english\HTML\
2. Right-click on the frameset.html and select properties from the shortcut menu
3. If an Unblock button is present in the properties dialog then select it.
4. Repeat this process for other HTML files in the folder if they are blocked
5. Re-launch the SOLIDWORKS Installation Manager process

Unblock HTML

Solution #2: Reset Internet Browser

Try resetting your Internet Browser options to default, close the browser and re-launch the SOLIDWORKS Installation Manager.
This could also be caused by a Microsoft Internet Explorer security update mentioned at http://support.microsoft.com/kb/967941.  Try uninstalling through Start > Control Panel > Programs and Features > View installed updates.  Uninstall KB967941 if possible and follow Workaround Method 4 from the web page.