SportScope Logo

SportScope

 

 

> Home

About Me

Our Family

My Hockey Times

Other Activities

Gandharan's JUTLA's

Field Hockey

Microsoft® Exchange

MAILSweeper 4.3

RIM - Blackberry

Contact Me

 

http://www.jutla.com/images/topright.gif

 

 

 

NetAPP
Removing the busy .rws snapshots from LUN

Exchange
UDP Refresh Issue in OL2002
How to run DCDiag ?
Outlook's Autocomplete Cache
Publishing a *.oft
How to recreate a .STM file
Exchange Server Maintenance Tasks
Exporting AD information using CSVDE / LDIFDE
Adding Disclaimers in Exchange
Cleaning SMTP queues from a spam attack.
Implementation of Secure Certificate for Windows Mobile
Creating a Resource Meeting Room Acceptance setup
How to collect the ObjectGUID from AdsiEdit
How to collect the ObjectGUID from PFDAVADMIN
How to take a dump from LDP
Setting default Recurring Meeting End-date
Uninstalling Exchange 2003

Removing Corrupted Calendar Entry
Messaging Interface has returned a unknown Error (OL2002)

Others
Lightscribe CD troubleshooting

Messaging Interface has returned a Unknown Error (OL2002)
In Outlook, if you get this issue it could be that the Mailbox has exceeded its mailbox limits, or sometimes it could be that you need to clear the cache (frmcache.dat) file

How to Create a Resource Meeting Room setup
1.Create a Resource meeting Room (same as any other mailbox) i.e. MeetRm 2.Create a new mailbox which is the Acceptance meeting room i.e. MeetAccept 3.Make MeetAccept a delegate of MeetRm
4.Make sure MeetAccept is Editor permissions on Mailbox, Calendar for MeetRm 5.Ensure that for both MeetRm and MeetAccept mailboxes, “processing meeting requests” options have he following options set.
6. Leave machine logged into MeetAccept profile

http://www.jutla.com/images/winat.jpg

Implementation of Secure Certificate for Windows Mobile
1. Register your web domain name Klingon.jutla.com and associate domain with incoming IP address
2. Create the certificate of name Klingon.jutla.com request for the Front-End Exchange server and save the text file
3. Go to www.verisign.co.uk and request for a root authority certificate
4. 24 hours later, Verisign will send the root authority certificate
5. On the Exchange Front-End server install the certificate
6. Then Export the certificate as a .PFX file with a password
7. On the Outside facing ISA box, Import the .PFX file to the Personal\Root area
8. In ISA Management set Web Listener to root certificate just imported and choose incoming domain as Klingon.jutla.com
9. Export the certificate as a .CER file and copy to all client devices requiring access to email

Removing a corrupted Calendar Entry
If you feel you have a corrupted Calendar Entry, you can do the following:

·          Change the Calendar view to by Category and not group by any fields

·          Create a new Folder as a Calendar item

·          Select all Calendar Entries, right-click and select “Move items to Folder” – to this new folder

·          Then using MCFMAPI

·          Select Session, logon and display

·          Logon using the mail profile of the Mailbox in question

·          Double-click on the users Mailbox

·          Expand Root Container

·          Expand Top of Information Store

·          Right-click and delete Calendar

·          Logoff and exit out

·          Start outlook using the /resetfolders switch

·          Select all calendar entries and move them back into the calendar

UDP Refresh Issue
This is a issue with XP SP2 - it increases the UDP timeout to 30 sec The fix is to create a new registry key as follows: HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\10.0\Outlook Create a new key and name it: RPC Within the new RPC key create a new 'Dword' Value and name it: forcepolling Give the new Dword value a value of '0'...

Uninstalling Exchange 2003
Uninstalling Exchange from Add/Remove Programs does not remove all files, it may leave some Registry entries but it will remove most so just follow that process unless you want to manually go and force removal.

http://support.microsoft.com/default.aspx/kb/833396

Running DCDiag
DCDiag /s:DomainControllername you must be member of domain admin group

Outlook's Autocomplete Cache
A popular feature request prior to Outlook 2002 was the ability to remember previously used addresses so that you could type a few letters in the To field and select an address from the drop down. All addresses used for new messages or replies are stored in an autocomplete cache file, at C:\Documents and Settings\

\Application Data\Microsoft\Outlook\profile_name.NK2. For most people, the autocomplete cache works great. A small percentage of users have problems with the file being deleted and recreated each time they close and reopen Outlook. While this should be no more than an annoyance, a growing number of users are relying on the autocomplete cache as a replacement for their address book and when the cache file is recreated, they lose the addresses stored in it.

Try a new Outlook profile and if it still gets cleared each time you close Outlook, you'll need to stop using the NK2 as an address book. If you need to save the addresses you reply to, use an add-in that adds address to the contacts folder automatically instead. Mapilab's Add Contacts, Sperry Software's Add Email Address are two of the many add-ins listed at http://www.slipstick.com/addins/contacts.htmdata that will create contacts for addresses you send email to or receive email from.

If you are using it as an address book, get Ingressor (http://www.ingressor.com) so that you can view and export the contents of the NK2 file daily. Exporting the contents frequently is important because the NK2 holds 1000 addresses. When it reaches 1000, the oldest, less used addresses are replaced.

Setting default Recurring Meeting End-date
When users create a Recurring meeting, No end date is specified as default.  This means that if you go to a date in the future i.e. 10/08/4500 it shows up there too – “feel free to attend the meeting”.  Now if we enter the following registry key (below), it will make the end date be 1 year from booking date as the default and you can change this by changing the days in the registry and it helps reduce Calendar size

 

[HKCU\Software\Microsoft\Office\11.0\Outlook\Options\Calendar]

"RecurrencesDefault"=365

 

Before

 

After


Publishing a *.oft
- file received as outlook template *.oft
- ensure correct name of the form is given by looking at the properties for the folder
- open the form in design mode
- publish it to personal library
- open and verify
- save original form
- copy new form from personal library to baring asset management org and overwrite it.
- also open the public folder and select the same form again and make sure you overwrite it the older one.
- inform user to check

How to recreate a .STM file
Reason: There a few reasons for *.STM file corruption:
a. Antivirus software periodically scanning the *.EDB or/and *.STM file.
b. The *.EDB or/and *.STM size increases significantly.
c. Hardware problem.

Creating the file: By using the instructions in this guide may lose important data, and therefore should be only used as a last resorts. It is recommend that you backup the databases before implement these instructions.

Always consider using a valid backup instead of these instructions. The amount of the data that you may lose depends on your mail client software - If everybody uses Outlook (MAPI protocol), then there will be very little user data in the .STM file. You may lose some in transit messages that haven't been delivered yet. If clients connect via POP3 or IMAP then most of their stuff will be in the .STM file, and its loss will be catastrophic to them. If clients use Outlook Web Access, messages will be in the .EDB file, but attachments sent will be in the .STM file.

1. Stop any antivirus software on the server.
2. Stop "Microsoft Exchange System Attendant" service. Note: This stage prevent from users to use the server.
3. Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
4. Navigate to: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan] In the right side of the screen change the value of "Enable" from 1 to 0.
5. Run eseutil /mh command to verity the need to recreate of the *.STM file:
    eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
    eseutil /mh "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"
6. Run eseutil /p /createstm command to create of the *.STM file:
    If the private mailbox store *.STM file may need to recreate, please use the following command:
          eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
    If the public store *.STM file may need to recreate, please use the following command:
          eseutil /p /createstm "C:\Program Files\Exchsrvr\MDBDATA\pub1.edb"
7. Go to "Start" -> "Run" and write "Regedit" and press on "Enter" button.
8. Navigate to: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\VirusScan] In the right side of the screen change the value of "Enable" from 0 to 1.
9. Start "Microsoft Exchange System Attendant" service.
10. Open Exchange "System Manager". Navigate to the problematic mailbox store/Public store.
11. Run "mailbox cleanup agent" on each mailbox store and choose "reconnect all mailboxes".
12. Optional: Open the problematic mailbox store/Public store, right click on the mailbox store/Public store and choose "properties". Press on "Database" tab and mark the checkbox "This database can be overwritten by a restore".
13. Mount the mailbox store/Public store. Note: If you Start "Microsoft Exchange System Attendant" service in phase 9, the mailbox store/public store should be mount automatically.
14. Start the antivirus software that was stop in phase 1.
15. Make full backup to the Exchange databases and the local server.

Exchange Server Maintenance Tasks Exchange 2003
Performs 11 tasks as part of its automated database maintenance schedule. Those tasks are:
1. Clearing the indexes on the mailbox and public folder stores.
2. Performing tombstone maintenance on mailboxes and public folders.
3. Removing expired messages from the dumpster for the mailbox and public folder stores. 4. Removing expired messages from public folders.
5. Removing deleted public folders with tombstones more than 180 days old.
6. Resolving message conflicts within public folders.
7. Updating server-version information on public folders.
8. Checking for and removing duplicate site folders on public folder stores.
9. Removing deleted mailboxes on mailbox stores.
10. Checking the message table for orphaned messages (messages with a reference count of 0).
11. Performing an online defragmentation of the Exchange Information Store (IS).

As you can imagine, performing all 11 tasks against an Exchange store can take quite a while, depending on the size of the database and the condition that the database is in at the beginning of the maintenance cycle. The problem is that Exchange must perform the maintenance tasks while causing the least possible impact on users. In most cases, this means performing the maintenance tasks at night, and doing so in a way that doesn't interfere with the nightly backup. This usually doesn't leave a lot of free time for IS maintenance.

Because time limitations might prevent all the maintenance tasks from running on a nightly basis, Exchange performs the tasks in a prioritized manner according to which tasks have run most recently and which tasks are most important. Fortunately, the priorities are simple. The first 10 tasks on the list have equal priorities. However, the 11th task (performing an online defragmentation of the IS) is considered more important than the other 10 tasks.

The first time that the Exchange maintenance cycle runs, it begins with the first task on the list and works through as many of the other tasks, in the order listed, as time allows. If the maintenance period reaches the point where only 15 minutes remain and not all the tasks have been completed, then Exchange must make a decision. If Exchange has spent the entire maintenance period on one task, and that task hasn't finished running, then Exchange will continue to spend the remainder of the maintenance period on that task. However, if at least one task has finished, Exchange makes note of that last completed task, aborts the current maintenance task, and begins an online defragmentation. Because Exchange considers an online defragmentation to be more important than the other maintenance tasks, it allows the defragmentation to run for as long as an hour after the maintenance period has expired.

The next time that Exchange encounters a scheduled maintenance period, it checks to see which task was the last one to successfully finish (not counting the online defragmentation). Exchange then launches the next task on the list. By not restarting at the beginning of the task list each night, Exchange is able to guarantee that each maintenance task runs occasionally

Exporting AD information using CSVDE
csvde -d "OU=Users,OU=UK,DC=Mydomain,DC=myroot,DC=net" -s testsvrdcs04 -f export.csv

This is to do the Export using the modified file in export.csv csvde -d "OU=Users,OU=UK,DC=Mydomain,DC=myroot,DC=net" -s testsvrdcs04 -f export.csv
To do the import using ldifde ldifde -i -f import.ldf -s Testsvrdcs004 /v

AD - Export members of Security Grp
dsget group "CN=Company Stock Score,OU=Groups,OU=UK,DC=mydomain,DC=myroot,DC=net" -members > ssrw.txt

type ssrw.txt
"CN=Nolan,OU= Accounts,OU=Users,OU=UK,DC= mydomain,DC= myroot,DC=net"
"CN=Bert,OU= Accounts,OU=Users,OU=UK,DC= mydomain,DC= myroot,DC=net"
"CN= Dude,OU= Accounts,OU=Users,OU=UK,DC= mydomain,DC= myroot,DC=net"
"CN=Jack,OU= Accounts,OU=Users,OU=UK,DC= mydomain,DC= myroot,DC=net"
"CN=,OU= Accounts,OU=Users,OU=HK,DC= mydomain,DC= myroot,DC=net"
" CN=,OU=Normal Accounts,OU=Users,OU=UK,DC=mydomain,DC= myroot,DC=net"

DSGET / DSQUERY etc. is built into 2003

Run the following to get teh full Exchange name of the group if in doubt
dsquery group -name "List name"
output will be "CN=List name,OU=Groups,OU=UK,DC=domain,DC=root,DC=net"

To get a list of all members of grp list name run the following command
Run dsget group "CN=list name,OU=Groups,OU=UK,DC=domain,DC=root,DC=net" -members displays all accounts that are a member of this group

This gives a list of all groups the user is a member of
dsget user "CN=jutlak,OU=Admin Accounts,OU=Admins,OU=UK,DC=jutla,DC=jutlaroot,DC=net" -memberof

LDIFDE
To get a list of all users
ldifde -f delegates.txt -d "ou= Accounts, ou=user, ou=UK, DC=mychildomain, DC=myroot, DC=net"

To get a filtered list of only Delegate Information and to display user name
ldifde -f delegates.txt -d "ou= Accounts, ou=user,ou=UK, DC=mychildomain, DC=myroot, DC=net" -l cn,publicDelegates,publicdelegatesBL

Adding Disclaimers in Exchange
What If you need to add an outgoing disclaimer to all mail on Exchange 2003 ?

On an Exchange 5.5 box you could use the IMSEXT.dll command and edit the registry with the information. But you cannot use the IMSEXT.DLL on Exchange 2003, it's reserved for use within Exchange 5.5 environments only.

For Exchange 2003 the options include going with a third-party solution, such as Mailsweeper or you can implement an event sink as described in Microsoft Knowledge Base Article 317680 "How to add a disclaimer to outgoing SMTP messages in Visual Basic script". The event sink option relies on a VBScript

Cleaning SMTP queues from a spam attack.
I've seen a loot of questions in different newsgroups about how to clean SMTP queues from a spam attack.

The easiest way to do this is to use the Advanced Queuing Administration Command Line Interface tool (aqadmcli.exe)

Run aqadmcli.exe from a command line with the following syntax to delete all messages from all queues: setserver "Servername" delmsg flags=all Run aqadmcli.exe from a command line with the following syntax to delete all messages from a specific sender address: setserver "Servername" delmsg flags=sender,sender=sender@domain_name.com

You can download aqadmcli.exe from: ftp://ftp.microsoft.com/pss/Tools/Exchange%20Support%20Tools/Aqadmcli/aqadmcli.exe

Outlook meeting requests: Essential do’s and don’ts
Have you ever heard someone say, “We are meeting at 3:30 today? I never saw the meeting request!"? Whether you schedule or attend a meeting, you can help it run smoothly and on time with the following meeting request do’s and don’ts:

Make a choice Accept, accept as tentative, or decline each meeting request that you receive, especially if it is an update to a meeting request that you previously accepted. By making a choice, you keep the meeting organizer apprised of your decision and you prevent the meetings that you want to attend from being accidentally deleted. If you need to attend a meeting but can't at the time it is scheduled, you can propose a new time for the meeting.

Try not to delete a meeting request outright because this is one way that meetings get "lost."

Send updates After modifying one of your own meeting requests, remember to click Send Update to send the updated request to all recipients.

Cancel a single meeting If you need to cancel a meeting, it is considerate to notify the people you invited. Delete the meeting from your calendar, click Send cancellation and delete meeting, and then send the cancellation to everyone you invited

Cancel recurring meeting If you, as the meeting organizer, are ending a recurring series of meetings, open the meeting on your calendar, set a new end date, and then send an update. This keeps the past meetings on everyone’s calendars, but future occurrences after the end date are removed.

Change meeting organizers If a recurring meeting is changing to a new organizer, there is not a way to reassign the ownership of the meeting. The original organizer should send an update with a new end date — the past meetings remain on everyone’s calendars, but future occurrences after the end date are removed. The new meeting organizer should send a new meeting request for meetings in the future.

Keep meetings from vanishing If you run Outlook on two computers and accept a meeting while using one of them, don't delete the meeting request from the Inbox on the other computer. If the request is still there, accept it again. Deleting a request on one computer after accepting it on another computer can cause the meeting to disappear from your calendar.

Process meeting requests and updates from the Inbox Always accept or decline a meeting request from your Inbox. Yes, Outlook allows you to accept or decline a meeting from its time slot on your calendar, but that can leave the meeting request in your Inbox. Leaving the meeting request in your Inbox might confuse you later and definitely leaves any delegates (delegate: Someone granted permission to open another person's folders, create items, and respond to requests for that person. The person granting delegate permission determines the folders the delegate can access and the changes the delegate can make.) you appointed wondering about whether the meeting was accepted.


Keep your meeting notes separate As a meeting attendee, avoid adding your own private notes to the body of a meeting request in your calendar. If the organizer updates the meeting, your notes are lost.

Don't move meeting requests Don't move a meeting request from your Inbox to a different folder before you accept or decline the request or before the meeting appears in your calendar.

Soon after a meeting request arrives in your Inbox, a piece of Outlook code — nicknamed the "sniffer" — automatically adds the meeting to your calendar and marks it as tentative. This is a fail-safe to keep you from missing the meeting in case you don't see the request in your Inbox. However, the sniffer doesn't reply to the meeting organizer. You still need to do that by accepting, accepting as tentative, or declining the request.

If you or a rule that you create moves an incoming meeting request from your Inbox before the sniffer can process the request, the meeting never appears in your calendar, and you might miss the meeting.

May Gurtej come, too? If you receive an invitation for a meeting and believe someone else should also attend it, instead of forwarding the meeting request to that person, ask the meeting organizer to add that person to the attendee list, and then to send everyone an updated meeting request. This avoids suprising the organizer with an unexpected attendee and helps prevent lost meeting requests.

There is always room for one more If you are the meeting organizer and you want to invite another person after sending the original meeting request, add the person to the attendee list (the To line) of the original meeting series or occurrence, and then send an update to all attendees.

Convert an appointment to a meeting request If you want to create a meeting from an appointment on your calendar, open the appointment, click Invite Attendees, and then select the people you want to invite. This converts the appointment to a meeting request.

Remove it right If you receive a meeting cancellation, click Remove from Calendar to remove the meeting from your calendar. Deleting the cancellation from your Inbox won't remove the meeting from your calendar.

Try not to change an existing attendee list Suppose the attendee list in one of your meeting requests contains two instances of a person's name. If you delete one of the names, and then send a meeting update to the "Removed or Added Attendees," the person receives a cancellation. Similarly, if you send the meeting update to "All Attendees," the person receives both a cancellation and an update.

Be careful with DLs Try to avoid sending meeting requests to distribution lists (DLs), particularly ones that you are a member of. If you need to invite all the members of a distribution list, expand the list in the To line before sending the request. If you need to add or remove attendees from a meeting request that you already sent to an unexpanded distribution list, don't expand the list and start adding or deleting names. Instead, cancel the meeting and create a new one.

Don't auto-accept requests If you have granted one or more persons delegate access to your calendar or if you have delegate access to someone else's calendar, turn off automatic acceptance of meeting requests. By turning off automatic acceptance you avoid problems with delegate workflow.

Avoid calendar clutter To make people aware of your schedule, or to let them know when you plan to be away from the office, don't send a meeting request or forward appointments that block out portions of your schedule on their calendars. Instead, share your calendar with them.

If you don't want to share your calendar, you can still use a meeting request to let people know when you will be away from the office. Before you send the meeting request, set Show time as to Free so that it doesn't block out the time that you are away as Busy or Out of Office on the other people's calendars.

So what if someone sends a meeting request or appointment that blocks out portions of your calendar? If you accept the item (item: An item is the basic element that holds information in Outlook (similar to a file in other programs). Items include e-mail messages, appointments, contacts, tasks, journal entries, notes, posted items, and documents.), set Show time as in the item to Free.

If you don't want to receive meeting request responses... Typically, it is best to know in advance who plans to attend a meeting that you schedule. By default, Outlook meeting requests ask for a response from each person you invite. You have the option not to receive responses to your meeting request, but then you won't know who accepts, accepts as tentative, or declines it.

To collect the ObjectGUID from AdsiEdit:


1)    Open ADSI Edit

2)    Expand your domain

3)    Expand the DC folder

4)    Click Microsoft Exchange System Objects folder

5)    Right click on  the name of your PF in the details pane on the right

6)    Click properties

7)    In the attribute editor tab, double click “objectGUID”

8)    Copy the value shown and paste into a new .txt file named ADSI and PFDAVAMIN.txt

9)    Save the .txt file but do not close

10)  Close all ADSI Edit windows.


To collect the ObjectGUID from PFDAVADMIN:

1)    Open PFDAVADMIN

2)    After connecting expand Public folders

3)    Right click the name of your public folder

4)    Click “Property Editor”

5)    From the “Property” drop down box select “PR_PF_PROXY: XXXXXXXX” (The X’s represent numbers)

6)    Then click “Execute”

7)    Copy the text displayed into the .txt file you still have open (ADSI and PFDAVAMIN.txt)

8)    Save and close the .txt file

9)    Close all PFDAVADMIN windows.

 

To take a dump form LDP:

1)    From cmd prompt type ldp and press enter

2)    Click “Connection” then “Connect”

3)    Enter the requested details and click ok

4)    Click on “Connection” again and click “Bind”

5)    Again, fill in the requested details. These will need to be an administrators details. Click ok

6)    Now click “View” and the “Tree”

7)    Choose your DC name from the list and click ok

8)    From the hierarchy on the left double click “CN=Microsoft Exchange System Objects ....”

9)    Now double click the “CN={YOUR PF NAME}, .....”

10)  Copy all of the text in the right hand side pane and save it to a new .txt file called LDPDump.txt

11)  Close all LDP windows.


Netapps
Removing the busy .rws snapshots from LUN.
Run the following command to see what snapshots the rws file still resides in: syntax: lun snap usage



http://www.jutla.com/images/netapp1.jpg

You then have to delete these .rws files which are locking the snapshot from the active file system.

We get another snap list and see the snapshot is still busy. This is because the rws file still resides inside a snapshot and is still being backed by the original lun.

Run the following command to see what snapshots the rws file still resides in: lun snap usage

http://www.jutla.com/images/image010.jpg

Above you can see the snapshot names that contain the rws file circled in red
Delete the snapshots using the command:
Syntax:
snap delete


snap delete class snapshot5
snap delete class snapshot4
snap delete class snapshot3


Lightscribe CD
http://www.nero.com/nero7/eng/FAQs_Nero7_LightScribeLabelflash.html
Here you will find answers to questions about LightScribe and LabelFlash

Where can I find the LightScribe function in Nero?
You will find the Lightscribe option in the menu "Extras" in Nero StartSmart. If you start Lightscribe by clicking the button, you will get the option “Data label”. This option does not allow to create a “full-face” label. To do so close the compilation and start a new compilation. The Lightscribe option is also available in Nero Express and in Nero Cover Designer

Where can I find the LabelFlash function in Nero?
You will find the Labelflash™ option in the menu "Extras" in Nero StartSmart as well as in Nero Burning ROM and in Nero Express (click on the little arrow on the left side of the Nero Express window). Nero Cover Designer does not offer the Labelflash™ option.

My LightScribe recorder is not recognized by Nero. Why?
Nero fully supports LightScribe Direct Disk Labeling.LightScribe technology requires four elements: LightScribe enabled CD/DVD recorder LightScribe compatible CD/DVD Nero 7 or Nero 6 Reloaded (Nero 6.6.0.8 or later version installed) LightScribe Host Software must be installed. It can be downloaded from our website: http://dl1.nero.com/LS_HSI.EXE

Please download the user guide from our website to learn more about LightScribe: » NeroLightScribe.chm. If the LightScribe function does not work in your LightScribe burner, please check the following settings:
In Windows, go to -->Start -->Settings -->Control Panel -->Administrative Tools -->Services -->LightScribeService Direct Disc Labeling Service
Right-click on "LightScribeService Direct Disc Labeling Service", choose "Properties",
go to "Startup type" and select "Automatic".
The display under "Service status" has to be set to "Started".
In Windows, go to -->Start -->Settings -->Control Panel -->Administrative Tools -->Local Security Policy -->Local Policies -->Security Options
Double-click on the entry "Devices: Restrict CD-ROM access to locally logged-on user only".
Choose the option "Disabled". Confirm this change by clicking on "Apply” and "OK".
If you use Windows XP Home, please try the following steps: Open the "Registry" by clicking on “Start” in Windows, clicking on “Run”, typing in "regedit" into the field "Open" and verifying with "OK".
Select the path "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\Current Version\Winlogon" Doubleclick the entry "allocatecdroms" and check if the value is set to "0". If not, please set it to "0".
Stop and restart the service "LightScribe" in the control panel. In Windows select -->Start -->Settings -->Control Panel -->Administrative Tools -->Services Now the Lightscribe function should be recognized.
Please also change a setting of the Lightscribe service: Rightclick on the service "Lightscribe", select -->Properties -->Recovery Select the option "restart the service" in the field "first failure". The option "restart service after 1 minute" will now be activated.
Confirm this setting with "Apply" and "OK".

If I burn a disc with Nero Express I always get the option to create a Lightscribe label. How can this option be disabled?
You can disable the LightScribe option in Nero Express. Click on the little arrow on the left side of the Nero Express window, select “Options”. Uncheck the box „always print LightScribe Label“.


The guardian angels of life sometimes fly so high as to be beyond our sight, but they are always looking down upon us." ~Jean Paul Richter~