Redirect print server webpage in a 2008 R2 Failover Cluster.

I am configuring a 2 node 2008 R2 Failover Cluster with print services as a resource. On a client, i can install a printer by going to the website http://virtualprintserver.domain/printers/, selecting a printer and click on connect.
To prevent showing the default IIS page, i want to redirect http://virtualprintserver.domain to http://virtualprintserver.domain/printers/.
How can i achieve this? I have searched in IIS manager, but could not find anything.
Thank you for your help.

Solved!
After consulting a colleague with web design knowledge we came up with the following solution:
Go to %SystemDrive%\inetpub\wwwroot\
Rename iisstart.htm in iisstart.htm.old
Create a new index.htm file with the code: <html><head><title></title><meta http-equiv="refresh" content="0;URL=http://virtualprintserver.domain/printers" /></head><body></body></html>
Reset IIS

Similar Messages

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

How to install a database on a MS Windows 2008 R2 failover cluster?

Hello,
I have to install a Oracle 11g R2 database onto a MS cluster (Windows Server 2008 R2 Failover Cluster with 2 nodes and shared storage). I installed the DBMS on both nodes. On the first node, I created a tablespace, the files are on the shared storage. I can connect to that database, up to here everything is fine.
But the problem is: How do I have to configure the DBMS on the second node to use the existing database files in the case when the second node gets the Cluster IP and the shared storage? The switchover is done, all database files (in the filesystem) can be seen on the second node.
The goal is to connect to the database from an external application, regardless which node is active.
I know the "Oracle Fail Safe Manager", it is already installed on both nodes.
A link to the related documentation would be helpful, I can't find anything.
Best regards,
C. Jost
Edited by: user13250186 on 07.06.2010 09:40

Hello,
But the problem is: How do I have to configure the DBMS on the second node to use the existing database files in the case when the second node gets the >Cluster IP and the shared storage? The switchover is done, all database files (in the filesystem) can be seen on the second node.When you switch the database from one node to another one do you have any error ?
Can you connect to the database and check for the Tablespaces ?
Normally, with OFS you define Groups. In one Group you'll have the Database, the Disk, the IP address and the Listener. So when you move the Group from one node to another one, the disk will be recognized on the second node then, the database, listener, ... will start and, there's no reason to loose a datafile.
Please, find enclosed, an introduction to Oracle Fail Safe concept:
http://www.oracle.com/technology/tech/windows/failsafe/pdf/fisc32.pdf
Hope this help.
Best regards,
Jean-Valentin

Microsoft update KB 3002657 and 2008 R2 failover cluster for virtualization

After installing Microsoft update KB 3002657 on my Windows 2008 R2 failover cluster for virtualization, nodes in cluster lost connection to CSV and all my VM's were moved to node owning the volume.
I lost whole day to solve that problem.
But should i keep that update not installed on cluster nodes or anyone maybe has a solution for that ?

Hi a3pl,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior from the cluster perspective. Please offer us
more information such as the failover cluster validation error, the failover error event ID, with the current information it is difficult to presume which part may cause this issue, we strongly suggest you install the following update when you use failover
cluster.
Recommended hotfixes and updates for Windows Server 2008 R2-based server clusters
http://support.microsoft.com/en-us/kb/980054
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Server 2008 R2 failover cluster for DFS servers

A new client currently has a couple Server 2008 R2 failover clusters (one at each of their two primary sites) as their two hub DFS locations. I'm confused, and can't see much of a reason for this implementation, which only seems to introduce added complexity
with no real benefits. Here are my reasons:
- At each site, the servers in the failover clusters are on the same server VM farms, hosted on the same SAN's.
- The data hosted on each node of the clusters are not identical. For example, server1 has 25 DFS replicated folders and server2 has 20 replicated folders. In fact, the ~25 folders on server1 are all named <site>-user, and the ~20 folders on server
2 are <site>-data. There appears to be no crossover.
So if the SAN fails, they're screwed. If the VM host fails, they're screwed. Why not just have two DFS servers at each site for redundancy within each site, and replicating with other site DFS servers as needed? I'm not super strong with failover clustering
at all though, so I may easily be missing something.

Hi Steve,
From the description, as you said it seems create more factors which may cause a failure.
Using DFS on cluster could eliminate the possible of a single failing VM. However if the VM host is down, which will still leads to a failure. So actually the risk is still them same as just creating DFS namespace on these 2 VM hosts or any other file server.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

The acount information could not be verified - SQL 2005 SP3 installation on Windows 2008 R2 Failover Cluster

Hi,
We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
The problem is described bellow:
We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
We have tried to give the SQL services startup user on remote user account screen but the error is the same.
the domain administrator account exists on security logins of SQL with sysadmin rights.
Can someone help?
Thanks.

Hi StelioMavro,
According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
http://www.sqlcoffee.com/Tips0007.htm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

How to test node failover in Windows 2008 R2 Failover Cluster?

Can anyone give me advice on how to properly test a node failure with a 2 mode Failover Cluster in Windows 2008 R2?

To test the failover of a clustered service or application
In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click
Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster that you want to configure.
Expand Services and Applications, and then click the service or application for which you want to test failover.
Under Actions (on the right), click Move this service or application to another node.
As the service or application moves, the status is displayed in the results pane (center pane).
Optionally, repeat step 4 to move the service or application to an additional node or back to the original node.
Source page:
http://technet.microsoft.com/en-us/library/cc754577.aspx
Regards,
Housam Smadi

MS- WIN SERVER 2008-R2 FAILOVER CLUSTER --ERROR 1127 ,1583

DEARS ,
I HAVE BEEN FACING PROBLEM FOR MY WINDOWS FAIL OVER CLUSTER SCENARIO.
THE ERROR CODES ARE 1127 AND 1583 WHICH ARE STATING THAT
All nodes IPv4 networks should be configured properly.
Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster. If the adapter is to be used by Windows Failover Cluster, the IPv4 properties of the adapter should be changed to allow assignment
of a valid IP address that is not in the APIPA range.
However , I have checked that all of my NIC adapters have valid Static IP addresses. Also , when one of the nodes is down ,it cannot look for another node.
Please advise for the solution.

Hi,
Could you clarify your described “Nodes which are using Automatic Private IP Address (APIPA) for adapter Cluster.will not be added to the Windows Failover Cluster.” Did you
found one of your cluster node “automatically” have the APIPA address? If so, it seems is the IP conflict issue.
If it is not the IP address conflict issue, please try to disable your all the nodes firewall
or AV soft have the event 1583 typically cause by this function incorrect configured.
More information:
Event ID 1127 — Cluster Network Connectivity
http://technet.microsoft.com/en-us/library/dd353958(v=ws.10).aspx
Event ID 1583 — Network Connectivity and Configuration
http://technet.microsoft.com/en-us/library/ee830320(v=ws.10).aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to install DB6(DB2 for LUW) on a windows 2008 R2 failover cluster NodeB

Hi Gurus,
I am building a ECC6 EhP4 cluster on windows 2008 R2, I am following the installation guide chapter 7(document name: Installation guide SAP ERP6.0 EhP4 Ready SR1 ABAP on windows: IBM DB2 for Linux, Unix and Windows). But the step listed in the guide are not so clear and I have trouble for the database installation on the second node.
What I have done is:
1. 7.4.1 Preparing the database for MSCS step1 and 3
2. 7.4.2 Windows Server 2008: Creating the sap services and application
3. 7.4.3 Installing the central services Instance for ABAP (ASCS)
4. 7.4.4 Configuring the first MSCS node
5. 7.4.5 Installing the database instance on an mscs node(as i have done 7.4.1, i got some error in this step, then i checked some note and in note 1493410, it mentioned don't do step 7.4.1, so I uninstall the DB2, and get this step finished)
6. 7.4.6 Configuring the database for MSCS
7. 7.4.7 Configuring the Additional MSCS Node
8. 7.4.8 Installing an Enqueue Replicaiton Sever
9. 7.4.9 Installing the central instance
10. 7.4.10 Installing the dialog instance
Now I got problem on the database group, I cannot fail this to the second node. the DB2 Server resource cannot bring online to the second node. I think step 1, 4 and 5 may has some issue, but I don't know how should I install this database.
note 1493410's word confusing me, below is part of that note:
Chapter "Preparing the Database for MSCS"
You must not apply this chapter at the beginning of the installation. Instead, start the installation process with the next chapter "Configuring the First MSCS Node"
Follow the instructions in chapter "Preparing the Database for MSCS" in the exit step described in the chapter "Installing the Database Instance on an MSCS Node" before executing the db2mscs tool on the additional MSCS node only.
Point "3. Install all required operating system users ..." of this chapter is obsolete.
Anyone think my cluster still have chance to be fixed or I need rebuild it from scratch again. If I need build it again, I still don't know how to do the database installation on the second node
BR,
Peter

Hi pal,
Have you identified Ips and group names on which your sap application and DB should run..
I will give a overview...
Exam ples -
NODE A                  - 192.168.x.1
NODE B                   - 192.168.x.2 are the one which you idetify physical systems
1) Identify the drives you want to map for application and DB and make a partation and name the drives
2) Initially create Microsoft cluster service which creats cluster group----
CLUSTER GROUP   - 192.168.x.3 - Cluster name could be any thing meaningful...
Quorum disk          - 192.168.x.4 - 1 Gb drive
In point 2 if you are creating Cluster service with Heart ips you will naother ips for NODE A and NODE B ( 10.0.0.1 and 10.0.0.2)
3) Test and validate cluster configuration and ensure no erros are reflected
Above activities can be done with the help of OS Admin....
Now start working with SAP installation, even before that identify 2 names and ip address for SAP installation
Application group name can be as follows --
APPLPRD - 192.168.-x..5
Database group name can be as follows -
DBPRD - 192.168.x.6
You when you identify above drives for file systems and groups , you can start installation as mentioned in th guide...
Also let us know if you atrying to install EHP4 or EHP4.. as there some corrections to be followed in EHP4..
Open a new thread if you facing futher issues...
thanks,
rahuk

SQl 2008 R2 Failover Cluster does not failover after fresh install

I have installed a two node SQL Server 2008 R2 cluster. I used a Named Instance and the SQL Server and SQL Server Agent cluster resources are online on node 1. When I want to move the SQL Server group to node 2, the SQL Server resource fails to start (error
1205 and 1069).
I see in the application log that it is starting up database 'master'. After that I see: Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup etc...
It runs fine on node 1, so what goes wrong?

Hello,
Please verify DTC is configured correctly.
http://msdn.microsoft.com/en-us/library/dd897479(BTS.10).aspx
Please see the following resources also:
http://technet.microsoft.com/en-us/library/cc773525(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
http://technet.microsoft.com/en-us/library/cc773447(WS.10).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Windows 2008 R2 Failover Cluster - Netapp FAS6280 Black Screen on Restart when in cluster IGROUP

Hello everyone,
I've been working on this issue for a month now and have tickets open with Netapp and Microsoft. We have not been able to resolve the issue as of yet and since I'm losing all my hair I thought I should post it...
Scenario:
Two Windows 2008 R2 Enterprise SP Fail-Over Clusters (C1 & C2)
Two Netapp FAS6280 Filers for SAN storage
8 DELL R815 servers w/ 2x QLE2562 8GB FC HBAs all paths used (9.1.9.47 - newer did not resolve)
Netapp DSM 4.0 & SnapManager 6.4.2 (we also tried 1 rev newer, 1 rev older without luck)
C1 has 2 nodes & C2 has 4 nodes.
We are trying to add new nodes into the clusters. We were originally on EMC Clariion arrays and have been migrated to the netapp. Prior to moving we had 3 nodes in C2 and added node 4.
Now we want to add 2 more nodes, one to each cluster. We were able to configure the OS and get everything installed and matching the other nodes. we can assign HBAs to a test IGROUP and assign a lun, format it use it restart all is well and normal.
As soon as we change the HBAs to the IGROUP for C1 or C2's LUNs the servers don't want to restart properly. They hang at a black screen. The little green windows start splash screen runs the bar at the bottom. it then is supposed to fade
out and come back with the grey screen saying starting windows but that doesn't always happen. Sometimes it can take 4 hours to restart, or the machine will not come back onine at all. The pre-existing nodes *do not* experience this issue.
They restart in 5-10 minutes without issue.
We know drivers are part of the issue, but the maddening part is that it all works fine until we try to add the HBAs to the existing cluster storage group. We have a suggestion to create separate IGROUPs for each cluster node and add all luns to the
separate igroups. We configured this on one node and it still restarts long. We plan to modify the other nodes during our maintenance window and try again.
On the other cluster we were able to successfully complete the validate wizard and join. everything fails over and works except the server does not come up upon restart. If I unplug the HBAs it will come up fine, then I can plug them in and the
cluster functions.
Does anyone have any other ideas for us to try? Currently support for both netapp and Microsoft appear stumped. Sunday is our Window and we plan to try reconfiguring but I'm losing optimism...
Thanks for any feedback/ideas!
-Ryan

Thanks everyone who looked at this and offered feedback.
The issue appears to be resolved after the configuration change suggested by Netapp support.
The originally recommended configuration for our storage migration was similar to how I've seen storage groups configured on EMC arrays in the past. 1 storage group / igroup with all hbas/initiators for each host in the WFC/SQL cluster added to this
group. that group then gets all LUNs assigned to it.
The change in configuration that was recommended is to have 1 storage group / igroup for each host and put all initiators/hbas for each host in their own separate group. Then assign the all LUNs to each of the individual host igroups.
There is a lack of documentation on this, but it appears to work. We had 1 hit for separate igroups but had to go through a couple of support techs to get one to confirm this.
After applying this configuration in our change window today the issue is resolved. we were able to fail all resources onto the new node and restart it without issue. The question remaining for us is why the old systems continued to work while
the new nodes did not. The old nodes were originally migrated off an EMC and the version of ONTapp at that time was 8.1.2 and they worked fine.
We had upgraded to 8.1.3 to resolve an issue with flash cache and it seems like machines that we tried to attach to this igroup after that time did not work. all drivers software etc the same. We are wondering if this is somehow related and have
asked about it.
I wanted to update this thread, and perhaps it can save someone else some trouble down the line.
-Ryan

Migrate from Existing SQL 2008 R2 Failover Cluster (Rackspace) to new offsite SQL 2008 R2 Cluster (our own cloud)

I have an existing cluster sitting in Rackspace. We have a new co-location with its own SAN that we want to migrate everything over to. Now, if we were keeping the SAN active in Rackspace, this wouldn't be an issue and I'd just add two new nodes to the cluster
and take down the two old nodes, but I need the data shipped to the new SAN so everything in Rackspace can be turned off. VPN is configured between sites (500mbps pipe), so bandwidth isn't a problem.
Should I be adding new shared storage to the existing cluster, replicate to that, turn off the old shared storage, then add new nodes and eventually disable old nodes? I'm trying to do this with the least downtime.
The picture can best be described as this (very simplified)
RACKSPACE CLUSTER - on its own SAN
Node 1: SQLSERVER1-RACK
Node 2: SQLSERVER2-RACK
SQL Server Name: SQLSERVER
NEW CLUSTER - on its own SAN
Node 1: SQLSERVER1-NEW
Node 2: SQLSERVER2-NEW

while this might be doable using SQL Server replication, log shipping is best on a continual basis, or use a backup restore for a one time copy.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

2008 R2 failover cluster dns

Hello,
Wondering if there is any best practices when it comes to setting up DNS. Options are either dynamic DNS or add static A records for nodes and cluster name. Also I understand that there will be no DNS servers specified in TCP properties of the heartbeat
NIC.
Thanks

Hi,
please check "Network infrastructure and domain account requirements for a failover Cluster"
http://technet.microsoft.com/en-us/library/ff182359(v=ws.10).aspx#BKMK_Account_Infrastructure
The cluster should automatic register DNS records for ech cluster node and for the cluster name.
And yes, you do not need to specify DNS servers for heartbeat, livemigration or CSV NIC.
Hope that helps
Regards
Sebastian

Problems after print server migration to Windows Server 2008 R2

Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2.

Hi all,
New forum member, first time poster. I am at my wits end and have concussion from banging my head on the desk for several days running. Hopefully someone here may be able to help.
Environment
I have recently moved our printing environment from a Windows Server 2003 machine to a new Server 2008 R2 machine in prep for rolling out Windows 7 x64 clients. We have 30-40 printers, majority of which are HP's (M2727's, P4015dn's, CM3530's, P2035's & a CM8060).
My procedure for setting up the printers on the new server involved manually creating each printer and using up-to-date drivers, we wanted to start fresh. The HP's are all using the HP Universal PCL 5 or PCL 6 (61.115.1.10527) x86 & x64 driver. We use Desktop Authority on logon to install the required printers for each client.
Problems
Since everyone is now running through the 2008 R2 server we have had a bunch of intermittent problems pop up all over the place, mostly with our HP printers. When using the PCL6 driver some applications print a page or 10 of garbled gibberish (wingdings etc), so most printers are now using the PCL5 driver. Other applications print the error "PCL XL error" when using PCL6. Sometimes reinstalling the printer on the client machine will resolve these errors, however they tend to resurface.
When we use the PCL5 driver our M2727's intermittently report "Out Of Memory" on the printer display (they are stock with 64M RAM each) - upgrading the RAM may fix this but we never had this problem before on the 2003 server. This problem is not specific to the size of the printed document - it could be a 20 page report or a 2 page excel document. Resetting the printer will generally clear this issue temporarily. This is currently our most annoying/biggest issue.
Some people are having issues printing to a FujiXerox 340A-AP printer - in particular 1 person is able to print fine, where as another prints and the print margin appears to be far too small. After confirming all print margins on the server then reinstalling the printer on the client machine, the problem still persists. We have two FujiXerox printers, the second one is working as intended for 8-10 users with the exact same settings.
Attempted Fixes
These are some of the attempted fixes that I have tried:
Turning it off and on
Upgrading the firmware on the M2727's to resolve garbled printing & out of memory
Upgrading the firmware on the CM3530's to resolve garbled printing
Reinstalling all HP Universal PCL5/PCL6 x86 & x64 drivers on the print server
Ensuring that the 2008 R2 server is 100% up-to-date with MS patches
Backing up all printers on print server, removing the print server role, deleting all printers & drivers, rebooting, reinstalling the print server role and restoring all printers from backup
Upgraded Desktop Authority to the latest version - as this application is in charge of installing the printers on logon
As you can see we are having a lot of problems and nothing seems to make any sense. None of this happened before Windows Server 2008 R2 was brought in to the equation.
If anyone is able to provide any assistance that would be greatly appreciated.
Many thanks,
Hartz.
tldr; our printers are screwed since migrating to Windows Server 2008 R2.

Redirect print server webpage in a 2008 R2 Failover Cluster.

Similar Messages

Maybe you are looking for