- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Appliance Servers
- >
- PSA Migration Wizard Doesn't reapply Default Print...
Appliance Servers
1753451
Members
5865
Online
108794
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2003 02:25 AM
12-22-2003 02:25 AM
PSA Migration Wizard Doesn't reapply Default Printer Status
I have noticed a problem when distributing the Client Migration Wizard via login script. If the wizard is going to update a printer that is the end-user's default printer, that setting is not reapplyed to the new printer. When the end-user tries to print from Word or any other application, they get a message that they have no printer installed (which really isn't the case). Any application just makes a call for the "default printer" and when no printer has that title, it thinks that none exist. This can occur even if the end-use has only one printer installed. After the update and you browse the installed printers, the new printer, even if it's by itself, won't be set as default. Let me know if I missed a step. The end-user is WinXP SP1. PSA 4250
Brett
Brett
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP