Control of pop-up windows
When using Internet Explorer sometimes a large number of pop-up windows will open. These popups can be annoying and distracting. They occur, however, primarily as a result of non-work related use of the Internet. They also result from installing unauthorized software. Your computer and network access is provided as necessary to your work production. Few of the resources you access for work related purposes will have useless pop-ups. Because these problems are primarily the result of non-work related activity PeopleSoft resources will focus only on any related security issues, but not on resolving merely annoying behavior.
Not all "pop-ups" are from Internet Explorer. Windows Messenger, for example, reports the completion of the printing job or is used to send a message that your RAS session will be terminated because it exceeds allowed time. It can also be used to send information to your machine using your machine's IP address. Advertisers are beginning to make use of this tool. There is no relationship to visiting any web page. Look at the title bar of the popup to see if the window is related to Internet Explorer. Behind our firewall the use of windows messenger to send advertising should not be an issue. But outside the firewall the messages can be sent merely because the user is connected with access open to the Internet.
Look for and remove rogue software
There are some popups that result from rogue software you may have acquired from Internet browsing or from installing unauthorized software. For more information see Eureka! document 1 9036 — Unauthorized changes to I.E., or You Cannot Change Your Home Page Setting
Are the pop-ups error messages?
If the popups are error messages then start with document 19011- Internet Explorer Troubleshooting and FAQs to correct the cause of the errors.
If the popups are from Windows Messenger service, consider turning it off. 65001- Change the status of Windows Messenger service
Rebuild the machine
If the problem is sufficiently annoying then the resolution is to rebuild the machine and use more care in the future.
Use safe practices.
Avoid web surfing. The more often you access non-business sites, the bigger the risks.
Pay close attention to messages before answering. Many messages are worded to mislead you or make you think it is routine when really the wording has been changed.
Read all agreements closely. Permissions will often be buried in lots of boring terms so most people don't read them.
Make sure license terms are acceptable to PeopleSoft. If you aren't sure submit a ticket for license review. You are responsible and failure to ensure that license terms are acceptable can have serious consequences.
See the information in Eureka! document 69065 on safe computing practices.
Do not download tools from the Internet to try to resolve or prevent this problem.
Do not assume that because a program is well known, widely used or common that it is safe.
Do not accept an offer to update any software, including PeopleSoft licensed and installed software, unless that offer comes from PeopleSoft or you have confirmed that it is authorized by PeopleSoft. That includes offers from the original provider.
Do not install software that has not been licensed to PeopleSoft, including freeware. Typically the tools come with a waiver of liability, absolving the author of any responsibility for harm to your machine. This is not acceptable in the business environment. Software also should be tested for compatibility with business needs, and appropriate security before installation.
Do not install untested software. Many of our PeopleSoft applications rely on scripts, cookies, pop-ups and similar techniques to process information. It is likely that downloaded software intended to block these techniques will cause problems with our web based software. Furthermore, if you install software that results in a security compromise the consequences could be very serious, don't do it.
Created by the PeopleSoft Knowledge Management Team.
Copyright © 2003
All rights reserved.
Created: db 03/21/2003
Revised: db 06/11/2003