Printing a Configuration page on HP Printers

  1. Press the MENU key until the Information Menu appears in the printer display.
  2. Press the ITEM key until Print Configuration appears in the printer display.
  3. Press the SELECT key until Printing Configuration appears in the printer display. The Configuration page should print out now.

Remote Server Support | Remote Desktop Support

Leave a Comment

Windows 2003 R2 AD with SP2 – Network connections are empty

The Service Pack 1 for Windows Server 2003 changed the account that run the RPC service to NetworkService. I changed the account that run this service back to LocalSystem(same that without SP1), and the Network Connections service back to Started state

Remote Server Support | Remote Desktop Support

Leave a Comment

External Ntp server on windows dc

When you run the command: w32tm /resync, you receive the error: “The computer did not resync because no time data was available.” A warning is also posted to the event log: “Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator…”

Digging on the web, I found only more and more articles either repeating the steps from the Microsoft article or stating similar problems, with no solutions, to mine.

Firstly, let me declare the obvious: port 123 (SNTP) was forwarded to my domain controllers IP, both TCP and UDP, on my ADSL router. (NAT)

I tried my silver-bullet: unregister w32time and start again. I created the following batch script:

net stop w32time

w32tm /unregister
w32tm /register

w32tm /config /manualpeerlist: /syncfromflags:MANUAL /reliable:YES

net start w32time

w32tm /config /update

w32tm /resync /rediscover

The first line stops the NT service. You then unregister it and re-register it, recreating all the registry keys with default values, giving you a standard starting point. After that, I configure it, specifying an NTP server’s ip address as a peer (this IP is and that it should synch from the manual peer list. I also mark this server as a reliable time server. I then start the service again, tell it to update its configuration, just in case, and then resync.

Extra Steps :-

You have to be very sure you followed the instructions for using an external time source correctly. I’ve used these instructions on many a 2K3 server without issue, so to recap:

1. Change Windows to use the NTP protocol for time synchronization:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type
Value: Type
Data: NTP

2. Configure the AnnounceFlags value:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
Value: AnnounceFlags
Data: 5

3. Enable the NTP server value:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpServer
Value: Enabled
Data: 1

4. Specify the NTP server to use:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\NtpServer
Value: NtpServer

5. Select the NTP polling interval:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval
Value: SpecialPollInterval
Data: 900

6. Configure the time correction settings:
Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxPosPhaseCorrection
Value: MaxPosPhaseCorrection
Radix: Decimal
Data: 3600

Key: HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Config\MaxNegPhaseCorrection
Value: MaxNegPhaseCorrection
Radix: Decimal
Data: 3600

After this, stopping and restarting the NTP service should get you working. If it does not, check the value configured in step 4 – this being misconfigured is the only time I’ve seen errors in the Windows Time service like the ones you’ve posted, so it’s possible this is incorrect in your registry. I would also suggest using a time server OTHER than, as it is a VERY busy time server and you are likely to miss one or two time syncs to it before you get a good one. I would suggest using another time server, preferrably a stratum-2 NTP server closer to you. You can find these listed here:

Remote Server SupportRemote Desktop Support

Leave a Comment

fix for using USB Floppy drives for F6 drivers in Textmode

This fix will add support for USB floppy disks in the text mode portion of Windows Setup, and allow you to load F6 drivers.
This fix should work on Windows 2000 and up.
I have only tested it with a Sony USB floppy drive on Windows XP and Windows Server 2003 x64
Create your Storage device driver disk and open textsetup.oem
Add the following lines to the bottom of [HardwareIds.scsi.(device name)]
If this section does not exist you must create it!
If your USB floppy drive still does not work, look for the hardware ID in the floppy drive driver’s .inf file, and make sure any legacy floppy drives are disabled in the bios.

id = “USB\VID_03F0&PID_2001”, “usbstor” #–HP
id = “USB\VID_054C&PID_002C”, “usbstor” #–Sony
id = “USB\VID_057B&PID_0001”, “usbstor” #–Y-E Data
id = “USB\VID_0409&PID_0040”, “usbstor” #–NEC
id = “USB\VID_0424&PID_0FDC”, “usbstor” #–SMSC
id = “USB\VID_08BD&PID_1100”, “usbstor” #–Iomega
id = “USB\VID_055D&PID_2020”, “usbstor” #–Samsung

Leave a Comment

there was an error locating one of the items needed to complete this operation. it might have been deleted

You get this error when you try to configure outlook to connect to exchange.

To resolve this, close outlook and look for mapisvc.inf and delete this file, and restart your outlook.

Comments (16)

Add error on line 180: No Such Attribute

During SP1 installation you may get this error detail in ldif.err

in the ldif.err shows

Entry DN: CN=ms-Exch-Resource-Schema,CN=Schema,CN=Configuration,DC=buckleyschoolnyc,DC=org
Add error on line 180: No Such Attribute
The server side error is “The parameter is incorrect.”
An error has occurred in the program

You have to use adsiedit and modify some attributes in AD
go to the ms-Exch-Resource-Schema under schema configuration
then where it says display name if you see anything that says DUP with some numbers, remove the DUP and numbers and should just show the schema atrribute for example ms-Exch-Resource-Schema should show as ms-Exch-Resource-Schema not as DUP12312311ms-Exch-Resource-Schema

 Second go to
change ldapdisplayname that had a dup prefix and guid suffix to: msExchResourcePropertySchema

Leave a Comment

MSExchangeIS 9519 0x972: Public Folders Container Deleted, or Missing Required Attributes

The Microsoft Exchange Database Troubleshooter Tool detected one or more MSExchangeIS 9519 events with error code 0x972 in the Application log. This indicates a failure of public folder databases to mount because the Public Folders container has been deleted or is missing needed attributes.


This error can occur when the Public Folders container has been deleted from Active Directory, or if the affected Public Store is not configured to use the Public Folders container, that is, the value for the Public Folder containers msExchOwningPFTreeBL attribute does not point to the Public Store. The most likely cause for this error is that the Administrative Group that contained the Public Folders container was deleted without the Public Folders container first being moved to a new Administrative Group.

User Action

To resolve this issue, use the ADSI Edit, or a similar tool, to determine whether the Public Folders container exists and the msExchOwningPFTreeBL attribute is properly configured to point to the relevant Public Store.
To determine the cause of the error

1. Using ADSI Edit or a similar tool, locate each administrative group object in Active Directory.

The Administrative Group object can be found at:

CN=Configuration,CN=Services,CN=Microsoft Exchange,CN=Organization,CN=Administrative Groups,CN=Administrative group

2. Expand each Administrative Group and check for the existence of a CN=Folder Hierarchies container. If the CN=Folder Hierarchies container exists, highlight the container and verify that a CN=Public Folders object exists in the right-hand pane. If no CN=Public Folders object exists under any Administrative Group, move on to Solution 1, Recreate Folder Hierarchies and Public Folders containers. If you do find a CN=Public Folders container, proceed to step 3.

3. Right-click the CN=Public Folders object, and then click Properties.

4. In the Attributes list, select the msExchOwningPFTreeBL attribute, and then click Edit.

5. Make sure that the affected Public Folder Store is shown in the Values list. If it is not listed, proceed to Step 2

Step 1: Recreate Folder Hierarchies and Public Folders containers

Open adsiedit.msc.

Select Configuration-Configuration-Services-Microsoft Exchange-Orgname-Administrative Groups-Exchange Administrative Group.

Create the “Folder Hierarchies” under the Exchange Administrative Group

1. Right click on Exchange Administrative Group

2. Select New Object

3. Select msExchPublicFolderTreeContainer for the class and click Next

4. Enter the following for the value: Folder Hierarchies, click Next

5. Click Finish

Create Public Folder Tree Object

1. Right click CN=Folder Hierarchies -> New Object

2. Selected msExchPFTree for the class

3. For the value we entered, “Public Folders” and clicked next

4. Clicked on the “More Attributes” button, selected msExchPFTreeType and set the

value to 1. Note: This is very important that this value is set to a value of 1 as

this tells Exchange that this is a MAPI Tree

5. Click Ok and then finish

Step 2: Repopulating the value of the msExchOwningPFTreeBL attribute for the Public Folders container object

Populate msExchOwningPFTreeBL attribute object of the PF Stores in the organization

(Since this attribute is not directly editable, you have to follow the below steps

to do this for each PF store)

. Get properties of the newly created “Public Folders” Tree object in ADSIEdit.

2. Copy the distinguishedname value to the clipboard and then click cancel.

3. Navigate to the Storage group that contains the Public Folder Store for this

server and get properties of the server. In my case it was : Configuration – CN=Services – CN=Microsoft Exchange – CN= Administrative Group –
CN=Servers – CN=E2007 – CN=InformationStore – CN=Second storage group. Right click on CN=Public folder Database

4. Locate the msExchOwningPFTree attribute and paste in the value that was copied

to the clipboard in step 2. Click OK.

5. Restart the Information Store Service

6. Now try to  mount the PF store and see if we can access it fine now.

Comments (2)

Older Posts »