Category: Servers

Tuning Windows Servers for Performance
article #814, updated 828 days ago

Interesting material here:

https://msdn.microsoft.com/en-us/library/windows/hardware/dn529134

Categories:   Servers   

==============

Folder Redirection in Windows Server 2008 R2
article #797, updated 862 days ago

Here is a comprehensive document:

http://www.omegaits.net/articles/configuring-folder-redirection-in-windows-server-2008-r2

Categories:   Servers   

==============

Rename desktops in Windows domain
article #31, updated 891 days ago

There is a tool, part of the 2003 server reskit and included later on, which can rename desktops in a Windows domain. The command is very effective when run from a domain controller:

NETDOM RENAMECOMPUTER OLDNAME /newname:NEWNAME /userd:domain\domainadmin /passwordd:password /force /reboot:0

It does cause a reboot of the target machine.

Categories:   Windows OS-Level Issues   Servers

==============

Windows Firewall required to share printers in Server 2008 R2 and 7
article #558, updated 951 days ago

Windows Firewall is required, if network-shared printers are to be used, in Server 2008 R2 and Windows 7. See here:

http://support.microsoft.com/kb/2123653

But there are still many instances where Windows Firewall gets in the way. In these cases, set up a Group Policy for Windows Firewall with Advanced Security:

Computer Configuration,
Policies,
Windows Settings,
Security Settings,
Windows Firewall with Advanced Security,
Windows Firewall with Advanced Security – LDAP://cn={GUID},cn=….

and Allow all connections both inbound and outbound. That way the APIs all run, but no interferences.

Categories:   Windows OS-Level Issues   Servers

==============

Permissions for Quickbooks
article #764, updated 974 days ago

In addition to installation of the Quickbooks server piece, folder permissions have to be set correctly. Make sure you use the Advanced permissions settings area, and choose “This folder, subfolders, and files”.

The program folders have to give full control to “Users”:

http://support.quickbooks.intuit.com/support/Articles/SLN76845

and the data folders have to give full control to the service users created during installation of the server piece.

http://support.quickbooks.intuit.com/Support/Articles/HOW12213

Categories:   QuickBooks   Servers

==============

High disk usage by SBSMonitoring
article #689, updated 1202 days ago

Excellent instructions here:

http://www.itquibbles.com/sql-sbsmonitoring-high-disk-usage/

What is needed, in sum, is to rebuild the SBSMonitoring database.

Categories:   Servers   Windows OS-Level Issues

==============

Antivirus Exceptions: File Extensions Etc.
article #190, updated 1366 days ago

It is either essential or highly recommendable, to insert the following file extensions as exceptions to antimalware products, most especially on servers.

Exchange & Windows Search Indexing:

*.edb
*.stm

Microsoft SQL server and others (FTDATA is a filename, not an extension):

*.mdf
*.ldf
*.ndf
FTDATA
*.bak
*.trn
*.trc
*.sqlaudit
*.sql

StorageCraft:

*.spf
*.spi
*.spk

Acronis:

*.TIB

BlackBerry Enterprise Server:

*.pdb

Microsoft virtual machine:

*.vhd
*.vpc
*.vmc
*.vhdx
*.avhd
*.vsv

VMware:

*.nvram
*.vmdk
*.vmsd
*.vmsn
*.vmss
*.vmtm
*.vmx
*.vmxf

QuickBooks:

*.DES
*.IIF
*.ND
*.QBA
*.TLG
*.QBB
*.QBM
*.QBR
*.QBW
*.QBX
*.QBY

Quicken:

*.QDF
*.QEL
*.QPH
*.IDX
*.QSD
*.QDB

AutoCAD Inventor:

*.ipt
*.iam
*.idw
*.dwg
*.ipn
*.ide
*.prt
*.g
*.asm
*.neu
*.dxf

Borland Paradox, Pervasive SQL, SQLIte, AutoCAD, and others:

*.db
*.sdf
*.ddf
*.mkd
*.pvsw
*.s3db
*.s3db-journal

For Pervasive databases, in addition to the above, you can load the Monitor to see files and folders in use.

For PostGres databases, the files don’t have extensions; their names are all numbers, and they are in a single hierarchy per database. So find that hierarchy, and set up an exception for the topmost level, and you’re in.

For Oracle databases:

*.sql
*.lst
*.pls
*.plb
*.pks
*.pkb
*.pck
*.dbf
*.log
*.rdo
*.arc
*.ctl
*.dat
*.bad
*.dsc
*.ora
*.fmb
*.fmt
*.fmx
*.rdf
*.rep
*.rex

For MySQL databases:

*.frm
*.myd
*.myi

All the extensions above, in one swell foop:

*.edb
*.stm
*.mdf
*.ldf
*.ndf
FTDATA
*.bak
*.trn
*.trc
*.sqlaudit
*.sql
*.spf
*.spi
*.spk
*.TIB
*.pdb
*.vhd
*.vpc
*.vmc
*.vhdx
*.avhd
*.vsv
*.nvram
*.vmdk
*.vmsd
*.vmsn
*.vmss
*.vmtm
*.vmx
*.vmxf
*.DES
*.IIF
*.ND
*.QBA
*.TLG
*.QBB
*.QBM
*.QBR
*.QBW
*.QBX
*.QBY
*.QDF
*.QEL
*.QPH
*.IDX
*.QSD
*.QDB
*.ipt
*.iam
*.idw
*.dwg
*.ipn
*.ide
*.prt
*.g
*.asm
*.neu
*.dxf
*.db
*.sdf
*.ddf
*.mkd
*.pvsw
*.s3db
*.s3db-journal
*.sql
*.lst
*.pls
*.plb
*.pks
*.pkb
*.pck
*.dbf
*.log
*.rdo
*.arc
*.ctl
*.dat
*.bad
*.dsc
*.ora
*.fmb
*.fmt
*.fmx
*.rdf
*.rep
*.rex
*.frm
*.myd
*.myi

A different swell foop, better suited for some antivirus software:

*.edb;*.stm;*.mdf;*.ldf;*.ndf;FTDATA;*.bak;*.trn;*.trc;*.sqlaudit;*.sql;*.spf;*.spi;*.spk;*.TIB;*.pdb;*.vhd;*.vpc;*.vmc;*.vhdx;*.avhd;*.vsv;*.nvram;*.vmdk;*.vmsd;*.vmsn;*.vmss;*.vmtm;*.vmx;*.vmxf;*.DES;*.IIF;*.ND;*.QBA;*.TLG;*.QBB;*.QBM;*.QBR;*.QBW;*.QBX;*.QBY;*.QDF;*.QEL;*.QPH;*.IDX;*.QSD;*.QDB;*.ipt;*.iam;*.idw;*.dwg;*.ipn;*.ide;*.prt;*.g;*.asm;*.neu;*.dxf;*.db;*.sdf;*.ddf;*.mkd;*.pvsw;*.s3db;*.s3db-journal;*.sql;*.lst;*.pls;*.plb;*.pks;*.pkb;*.pck;*.dbf;*.log;*.rdo;*.arc;*.ctl;*.dat;*.bad;*.dsc;*.ora;*.fmb;*.fmt;*.fmx;*.rdf;*.rep;*.rex;*.frm;*.myd;*.myi

Categories:   Antivirus/Antimalware Tools and Issues   Servers

==============

Changing the DHCP Subnet Mask in Windows Servers, and DHCP Backup
article #464, updated 1825 days ago

Here’s a great step-by-step, using the ‘netsh’ command:

http://www.windowstricks.in/2009/06/how-to-change-subnet-mask-of-dhcp-scope.html

Categories:   Servers   

==============

32-bit printer driver in 64-bit server! And the other way around!!!
article #129, updated 1891 days ago

OK, so we have that problem increasingly common, a 64-bit server, trying to serve a printer to 32-bit client machines, or vice versa. It took me a while, but here are two different methods I have needed, depending on situation.

First, see if current drivers are downloadable for this printer in the server’s mode (bit-width). If they are, we are able to use method #1, which is probably preferable, although method #2 may still work too. Here’s method #1:

  1. Download them in both 32-bit and 64-bit versions, install the printer to the server in its preferred (32- or 64-bit) mode, and test. Unpack the other driver in a good location, you will need it soon.
  2. Get the printer properties up, go to the Sharing section, set up sharing. Don’t publish to the Active Directory yet or you might drive somebody crazy. Click on Additional Drivers.
  3. You’ll notice “x86” or “x64” is unchecked, because you haven’t installed the other driver yet. Check it, and then hit OK. The system will now demand to be directed to where you have unpacked the other driver. Do so. It might work just at this point! But…
  4. …it may ask you for one of two additional things. It may ask for 32-bit install media; or, it may ask for particular files, e.g., ntprint.inf, or ntprint.in_, in 32-bit mode. It’s important to realize that the 32-bit requirement is for equivalent OS: a 2008R2 install requires files from 32-bit Windows 7, 64-bit Server 2008 requires files from 32-bit Vista, and 64-bit Server 2003 requires files from 32-bit XP. If you can supply these files, do it, and you’ll be done shortly; it has to be done just once per server, not per printer. If you cannot do this, you’ll need to use method #2.

If you cannot use method #1, or if there are no downloadable drivers for your printer, we go to method #2:

  1. If there are no downloadable drivers from the printer manufacturer, install the printer to the server using Windows built-in drivers. Under Windows 7 / 2008R2, there is a “Windows Update” clickable in the driver list, by which you can retrieve a much larger set of drivers than is included by default; this is highly recommended. The included Microsoft generics may help, there is a PCL6 and a PS.
  2. If there are downloadable drivers from the printer manufacturer, for the server OS, use them.
  3. Install the printer to the client. If you’re using Windows Update or built-in drivers on the server, use them on the client too. Otherwise, make sure that the client drivers are the same type as the server’s, i.e., PCL6 and PCL6, PCL5e and PCL5e, PS3 and PS3.
  4. On the client, log in as network administrator. Open up the properties of the printer. Click on Advanced. Click on New Driver. Notice the name of the wizard: you’re actually installing a driver onto the server, not onto the client!
  5. Choose the driver you want to install onto the server. Click Next et cetera. Watch the client driver install onto the server, over the network!
  6. Check it out the drivers on the server, Shared tab, Additional Drivers button. You’ll see one you need listed. You are done!
  7. If the New Driver method does not work, try doing approximately the same from within the Additional Drivers button; it works also, to add drivers to server from workstation, as long as you’re logged in as network admin.

Categories:   Printers & Printing   Servers

==============

SpoolerWin32SPL, Event ID 4
article #303, updated 2269 days ago

If you see a bunch of these:

SpoolerWin32SPL, Event ID 4
“The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-18\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing, or if the registry recently became unavailable.”

look for S-1-5-18\Printers\Connections in the registry. It probably goes down as far as “Printers”, but “Connections” is probably absent. Create it as an empty key, and the messages will stop.

Categories:   Servers