From http://support.microsoft.com/kb/318908
If you are using a Microsoft Outlook client computer, you cannot download an offline Address Book. When you try to download an Address Book in Outlook, the following error is logged in the synchronization log:
7:59:00 Microsoft Exchange offline address book
7:59:00 0X80004005
This issue may occur if the mailbox store has not been associated with a valid o...This issue may occur if the mailbox store has not been associated with a valid offline Address Book.
Back to the top
To resolve this issue, follow these steps: Start Exchange System Manager. Expand...To resolve this issue, follow these steps:
Start Exchange System Manager.
Expand Organization, and then expand Administrative Groups.
If "Administrative Groups" does not appear under Organization, make sure that you have configured Exchange System Manager to display Administrative Groups. To do so, right-click Organization, click Properties, and then click Display administrative groups.
Expand the administrative group to which the server belongs.
Expand Servers, expand the server that you want to configure, and then expand First Storage Group.
Right-click Mailbox Store, and then click Properties.
In the Offline Address Book section, make sure that a valid offline Address Book is listed.
If one is not listed, click Browse, and then click a valid offline Address Book. You can use Default Offline Address Book as the default setting.
Sunday, November 08, 2009
Thursday, October 22, 2009
How to test a Fax. (Free Fax Test)
HP Fax Test Instructions
To test the capability of your fax machine, follow the directions below.
NOTE: Be sure that your phone number is not Caller ID blocked by your telephone company prior to attempting to send and receive a fax. Pressing *82 before dialing the toll free number will unblock the Caller ID blocking feature in most areas. Other phone company services can prevent you from receiving a fax, including voice mail, call blocking, or call privacy features.
NOTE: Whenever troubleshooting a fax issue, it is good practice to set the Automatic Reports option to Every Error before attempting a test fax. This way, even if the sent fax fails, an error code will be generated that will guide you in future troubleshooting. This option is available in different places on different products, consult the product User's Guide for specific steps.
Send a one page black and white text fax to
1-888-hpfaxme (1-888-473-2963).
When your fax is received by the HP Test Fax Service, we will generate a return fax to you within five minutes confirming that we received your fax. This verifies that you can both send and receive a fax with your fax machine.
If you do not receive a return fax within 5-7 minutes, there may be a problem with the setup of your fax machine. Consult the user manual that came with the product for proper setup and configuration.
NOTE: The most common cause of failure is that the fax number set in the Fax Header on the machine does not match the number of the phone line connected to the fax. Also, ensure that the fax header contains the full 10-digit telephone number of the fax machine, including the area code.
To test the capability of your fax machine, follow the directions below.
NOTE: Be sure that your phone number is not Caller ID blocked by your telephone company prior to attempting to send and receive a fax. Pressing *82 before dialing the toll free number will unblock the Caller ID blocking feature in most areas. Other phone company services can prevent you from receiving a fax, including voice mail, call blocking, or call privacy features.
NOTE: Whenever troubleshooting a fax issue, it is good practice to set the Automatic Reports option to Every Error before attempting a test fax. This way, even if the sent fax fails, an error code will be generated that will guide you in future troubleshooting. This option is available in different places on different products, consult the product User's Guide for specific steps.
Send a one page black and white text fax to
1-888-hpfaxme (1-888-473-2963).
When your fax is received by the HP Test Fax Service, we will generate a return fax to you within five minutes confirming that we received your fax. This verifies that you can both send and receive a fax with your fax machine.
If you do not receive a return fax within 5-7 minutes, there may be a problem with the setup of your fax machine. Consult the user manual that came with the product for proper setup and configuration.
NOTE: The most common cause of failure is that the fax number set in the Fax Header on the machine does not match the number of the phone line connected to the fax. Also, ensure that the fax header contains the full 10-digit telephone number of the fax machine, including the area code.
Thursday, September 10, 2009
Why small businesses use Windows Small Business Server
Why small businesses use Windows Small Business Server:
http://blogs.technet.com/sbs/archive/2009/09/10/why-small-businesses-use-windows-small-business-server.aspx
http://blogs.technet.com/sbs/archive/2009/09/10/why-small-businesses-use-windows-small-business-server.aspx
Friday, August 28, 2009
SBS2008 not sending email out on a Dell PE2900
Issue with SBS2008 Sending email out on a Dell PE2900
Mail would receive just fine into the SBS2008 however sending email out would get stuck halfway and never get delivered.
No Return Bounce NO indication of any issues.
Found out that Broadcom NIC was the issue in the Dell PE2900
Even though it had Version 9 drivers Dell claimed that version 12 “Might”
I repeat “MIGHT” work.
Instead of dealing with it not working after new drivers, I disabled Onboard NICs
Purchased a DLINK 1GB Nic Card.
Installed and mail going out correctly now with no issues!
Information Courtesy of Lafayette Jefferson.
Mail would receive just fine into the SBS2008 however sending email out would get stuck halfway and never get delivered.
No Return Bounce NO indication of any issues.
Found out that Broadcom NIC was the issue in the Dell PE2900
Even though it had Version 9 drivers Dell claimed that version 12 “Might”
I repeat “MIGHT” work.
Instead of dealing with it not working after new drivers, I disabled Onboard NICs
Purchased a DLINK 1GB Nic Card.
Installed and mail going out correctly now with no issues!
Information Courtesy of Lafayette Jefferson.
Sunday, August 23, 2009
How to get WINS to work with SBS2008 over VPN
Info Taken From:
http://nicholas.piasecki.name/blog/2009/06/getting-wins-like-computer-name-resolution-over-vpn-in-sbs-2008/
By Nicholas Piasecki:
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
http://nicholas.piasecki.name/blog/2009/06/getting-wins-like-computer-name-resolution-over-vpn-in-sbs-2008/
By Nicholas Piasecki:
So this week concluded several sleepless nights and much heartburn as I migrated Skiviez’s SBS 2003 machine (running as our domain controller and our mail server) to SBS 2008. As far as things go, it went relatively smoothly, and the remainder of the week was dealing with lots of small niceties that I had forgotten that I had set up on the 2003 server that I now needed to set up once again.
One of these was something that I used for my convenience over a VPN connection from home. You see, the internal order processing application that I wrote uses some shared folders to store some temporary data, such as e-mails that are generated but not yet released to Exchange, or a local copy of images that are available on the Web site. This software–and our users–are used to referring to Windows file shares as \\COMPUTER-NAME\SHARE-NAME; for example, \\CYRUS\Pickup Holding, because for some reason some of the older servers are named after my boss’s dead cats.
When connecting through VPN to SBS 2008, however, that “suffix-less” name resolution was not working. So when \\CYRUS\Pickup Holding failed to resolve to anything, \\cyrus.skiviez.com\Pickup Holding would work fine. This was super annoying.
The reason this worked previously with our SBS 2003 installation is that it was acting as a WINS server, which provided this type of computer name resolution for us. SBS 2008 finally retires this ancient technology by default, however, so I had two choices: I could either install the WINS server role on SBS 2008, or I could just figure out how to get the 015 DNS Domain Name option from DHCP to relay through the VPN connection.
I chose the latter option, since it’s certainly less confusing to be able to say to someone in the future “we don’t use WINS, DNS does everything.” So here’s how to do it:
1.On the SBS 2008 server, click Start > Administrative Tools > Routing and Remote Access.
2.In the tree view, drill down past the server name to IPV4 > General. Right-click the General option and choose “New Routing Protocol” and choose DHCP Relay Agent.
3.Now right-click the newly appended “DHCP Relay Agent” node and choose Properties. Add the IP address of your DHCP server (which is probably your SBS server itself), and click OK. Then click it again and choose “New Interface” and add the “Internal” interface.
4.Now if you connect through VPN, an ipconfig /all should show your domain name as a “Connection-specific DNS suffix” and pinging machines by their suffix-less computer names should work. (If it doesn’t, make sure your DHCP server is using that 015 DNS Domain Name option, which the SBS 2008 wizards set up by default.)
Monday, August 17, 2009
WARNING: IE Security update KB963027 Breaks Companyweb (SBS2003)
Companyweb requires login but doesn't work.
The issue is that that you are prompted for credentials
(user/password) that will not be accepted under any conditions.
reguardless of what account you use.
One solution is to removing IE 7 Security update KB963027,
And then companyweb can be accessed again.
The issue is that that you are prompted for credentials
(user/password) that will not be accepted under any conditions.
reguardless of what account you use.
One solution is to removing IE 7 Security update KB963027,
And then companyweb can be accessed again.
Friday, August 14, 2009
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: ]
MSSQL$MICROSOFT##SSEE Event Error 18456 on your SBS2003 server.
This issue is generally related to WSUS 3.0 that uses Windows Internal Database (MSSQL$MICROSOFT##SSEE), and the event is logged because the permissions is not correctly set for 'NT AUTHORITY\NETWORK SERVICE' on the SUSDB database file, or the MSSQL$MICROSOFT##SSEE instance.
The suggestions are to check NTFS permission on the SUSDB, and grant login permission to 'NT AUTHORITY\NETWORK SERVICE' on the instance. To do so:
1. Check NTFS permission on the SUSDB folder:
------------------
a. Locate the SUSDB.mdb on the WSUS server. By default, it is under the UpdateServicesDbFiles folder such as C:\WSUS\UpdateServicesDbFiles\SUSDB.mdf.
b. Check the Security Permissions on the C:\WSUS\UpdateServicesDbFiles folder, and grant 'NT AUTHORITY\NETWORK SERVICE' Full Control permission
2. To grant 'NT AUTHORITY\NETWORK SERVICE' login permission on the instance:
----------------
a. Open a Command Prompt on the SBS2003 server, then run the following commands:
osql -E -S servername\Microsoft##SSEE
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE'
Note: Replace servername with the host name of the SBS2003 server
b. Restart the Microsoft##SSEE service, and update service.
This issue is generally related to WSUS 3.0 that uses Windows Internal Database (MSSQL$MICROSOFT##SSEE), and the event is logged because the permissions is not correctly set for 'NT AUTHORITY\NETWORK SERVICE' on the SUSDB database file, or the MSSQL$MICROSOFT##SSEE instance.
The suggestions are to check NTFS permission on the SUSDB, and grant login permission to 'NT AUTHORITY\NETWORK SERVICE' on the instance. To do so:
1. Check NTFS permission on the SUSDB folder:
------------------
a. Locate the SUSDB.mdb on the WSUS server. By default, it is under the UpdateServicesDbFiles folder such as C:\WSUS\UpdateServicesDbFiles\SUSDB.mdf.
b. Check the Security Permissions on the C:\WSUS\UpdateServicesDbFiles folder, and grant 'NT AUTHORITY\NETWORK SERVICE' Full Control permission
2. To grant 'NT AUTHORITY\NETWORK SERVICE' login permission on the instance:
----------------
a. Open a Command Prompt on the SBS2003 server, then run the following commands:
osql -E -S servername\Microsoft##SSEE
sp_grantlogin 'NT AUTHORITY\NETWORK SERVICE'
Note: Replace servername with the host name of the SBS2003 server
b. Restart the Microsoft##SSEE service, and update service.
Wednesday, August 12, 2009
How to Restore the Windows Logo Screen Saver Back in Windows 7
How to Restore the Windows Logo Screen Saver Back in Windows 7
http://www.sevenforums.com/tutorials/7226-windows-logo-screen-saver-restore.html
http://www.sevenforums.com/tutorials/7226-windows-logo-screen-saver-restore.html
Monday, August 10, 2009
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
Find Dell Current Server PC and Laptop Deals
These are not Paid Links (I get no Commission)
Just Posted here for a quick link to Dell Deals
Current Dell Deals:
Server - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-servers?c=us&cs=04&l=en&s=bsd
Desktop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-desktops?c=us&l=en&cs=04
Laptop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-laptops?c=us&cs=04&l=en&s=bsd&~tab=1&redirect=1
Just Posted here for a quick link to Dell Deals
Current Dell Deals:
Server - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-servers?c=us&cs=04&l=en&s=bsd
Desktop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-desktops?c=us&l=en&cs=04
Laptop - http://www.dell.com/content/topics/topic.aspx/us/segments/bsd/dell-deals-laptops?c=us&cs=04&l=en&s=bsd&~tab=1&redirect=1
Saturday, August 08, 2009
How to Switch from 32bit to 64bit or 64bit to 32bit in IIS7
Open a Command Prompt and enter the following Command Line
To Switch from x64bit to x32bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
-------------------------------
To Switch from x32bit to x64bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
-------------------------------
(The above command lines should all be one line)
.
To Switch from x64bit to x32bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 True
-------------------------------
To Switch from x32bit to x64bit
-------------------------------
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
-------------------------------
(The above command lines should all be one line)
.
How to allow more than 1 TS Admin Session in SBS2008
In SBS2003 you could have three admin sessions
1 at the console and 2 RDC.
this would allow you to use Shadow so two admins can view screens.
(Type Shadow in a dos box and see what it says for more information)
On SBS2008 By DEFAULT you cannot do this.
From the Run line in SBS2008 type
tsconfig.msc
Find the sections on Allow remote connections to only one.
and uncheck the box!
Then you can have your regular Two or more sessions in SBS2008
(just remeber only 1 in SBS console is allowed at a time.)
1 at the console and 2 RDC.
this would allow you to use Shadow so two admins can view screens.
(Type Shadow in a dos box and see what it says for more information)
On SBS2008 By DEFAULT you cannot do this.
From the Run line in SBS2008 type
tsconfig.msc
Find the sections on Allow remote connections to only one.
and uncheck the box!
Then you can have your regular Two or more sessions in SBS2008
(just remeber only 1 in SBS console is allowed at a time.)
How to Remote Manage PC's in SBS2008
In SBS2003 you could right click on the PC name on the server and click MANAGE!
On SBS2008 that feature is not visable.
On the server open "computer management"
and then from the file menu, connect to another computer.
Then you can manage the computer like before.
(I'm not talking about RDC here)
On SBS2008 that feature is not visable.
On the server open "computer management"
and then from the file menu, connect to another computer.
Then you can manage the computer like before.
(I'm not talking about RDC here)
Monday, August 03, 2009
Blackberry Wireless Carrier account links
====================================================
To set it up: Go to the respective carrier's site link below,
setup a new email address (keep your current carrier's email), add an
account, provide the Exchange email address, and hit next. Let it time out
when it says it can't find it, then tell it you'll set it up manually, then
set it up manually by indicating it's a corporate account using OWA, hit
next, provide the OWA address, user alias, etc.
Nextel:
https://bis.na.blackberry.com/html?brand=nextel
Sprint
https://bis.na.blackberry.com/html?brand=sprint
Verizon:
https://bis.na.blackberry.com/html?brand=vzw&locale=en
ATT/Cingular:
https://bis.na.blackberry.com/html?brand=mycingular
=================================================
-Posting information from Ace Fekay
To set it up: Go to the respective carrier's site link below,
setup a new email address (keep your current carrier's email), add an
account, provide the Exchange email address, and hit next. Let it time out
when it says it can't find it, then tell it you'll set it up manually, then
set it up manually by indicating it's a corporate account using OWA, hit
next, provide the OWA address, user alias, etc.
Nextel:
https://bis.na.blackberry.com/html?brand=nextel
Sprint
https://bis.na.blackberry.com/html?brand=sprint
Verizon:
https://bis.na.blackberry.com/html?brand=vzw&locale=en
ATT/Cingular:
https://bis.na.blackberry.com/html?brand=mycingular
=================================================
-Posting information from Ace Fekay
Tuesday, July 28, 2009
How to Repair the information store Exchange 2003 with the eseutil
Repair the information store:
At a command prompt, change to the drive:\Program Files\Exchsrvr\Bin folder, where drive is the letter of the drive on which Exchange is installed. Use one of the following commands:
If you are trying to restore the mailbox store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb", and then press ENTER.
If you are trying to restore the public folder store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\pub1.edb", and then press ENTER.
At the command prompt, type eseutil /mh "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to verify the consistency information that is returned.
At the command prompt, type eseutil /d "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to defragment and to compact the database.
At the command prompt, type ISINTEG -S Server_Name -FIX -TEST ALLTESTS, and then press ENTER. Repeat this several times until it reports zero fixes and zero errors.
Mount the store.
Back up the store.
At a command prompt, change to the drive:\Program Files\Exchsrvr\Bin folder, where drive is the letter of the drive on which Exchange is installed. Use one of the following commands:
If you are trying to restore the mailbox store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb", and then press ENTER.
If you are trying to restore the public folder store, type eseutil /p "drive:\Program Files\Exchsrvr\MDBDATA\pub1.edb", and then press ENTER.
At the command prompt, type eseutil /mh "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to verify the consistency information that is returned.
At the command prompt, type eseutil /d "drive:\Program Files\Exchsrvr\MDBDATA\priv1.edb" (or pub1.edb), and then press ENTER to defragment and to compact the database.
At the command prompt, type ISINTEG -S Server_Name -FIX -TEST ALLTESTS, and then press ENTER. Repeat this several times until it reports zero fixes and zero errors.
Mount the store.
Back up the store.
Monday, July 27, 2009
Remote Web Workplace Requires the Microsoft Remote Desktop Active X Control
Remote Web Workplace Requires the Microsoft Remote Desktop Active X Control
“This portion of Remote Web Workplace requires the Microsoft remote desktop Active X control. Your browser security settings may be preventing you from downloading Active X controls. Adjust these settings and try to connect again”
Option 1:
1.In IE7, go to the Tools menu.
2.Choose Internet Options > Programs > Manage add-ons.
3.Look for ‘Microsoft RDP Client Control (redist)’.
4.Click on it and then look below and click on ‘Enabled’.
If you can't find 'Microsoft RDP Client Control (redist)'
It maybe need to be re installed.
Try going into registry and deleting key
7584C670-2274-4EFB-B00B-D6AABA6D3850
Then it should prompt you into installing the active X again.
Option 2:
1.“Tools” menu > Internet Options > Advanced.
2.Now click on the Reset button at bottom to reset the IE7 settings.
3.Restart Internet Explorer and retry logging into Remote Web Workplace.
4.Download and install the Active X plugin.
Once you do that you should be able to log in to Remote Web Workplace also known as RWW.
“This portion of Remote Web Workplace requires the Microsoft remote desktop Active X control. Your browser security settings may be preventing you from downloading Active X controls. Adjust these settings and try to connect again”
Option 1:
1.In IE7, go to the Tools menu.
2.Choose Internet Options > Programs > Manage add-ons.
3.Look for ‘Microsoft RDP Client Control (redist)’.
4.Click on it and then look below and click on ‘Enabled’.
If you can't find 'Microsoft RDP Client Control (redist)'
It maybe need to be re installed.
Try going into registry and deleting key
7584C670-2274-4EFB-B00B-D6AABA6D3850
Then it should prompt you into installing the active X again.
Option 2:
1.“Tools” menu > Internet Options > Advanced.
2.Now click on the Reset button at bottom to reset the IE7 settings.
3.Restart Internet Explorer and retry logging into Remote Web Workplace.
4.Download and install the Active X plugin.
Once you do that you should be able to log in to Remote Web Workplace also known as RWW.
Wednesday, July 22, 2009
Thursday, July 16, 2009
FYI: Do not delete Computer Groups SBS2008 WSUS 3.0
Why? the Windows SBS Console Crashes when running reports
(And Daily Weekly Reports will have Stopped)
I ran into This last week and I thought I'd post it.
Running a report I get a Crash/Error
With Error
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
In log
C:\Program Files\Windows Small Business Server\Logs\console.log
there is a "NullReferenceException"
The problem was I deleted a computer group in WSUS 3.0
I deleted the Group "Update Service Excluded Computers"
(Since I felt it didn't matter since there were no computers in that group.)
Well WRONG it does matter Make sure you have all Groups.
Unassigned Computers
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers
Note "Update Service Excluded computer" and it should NOT be "Update
Services Excluded computer" which 'Services' is plural
If any groups are not in the list or the names are not exact same, the
report will crash.
Russ
(And Daily Weekly Reports will have Stopped)
I ran into This last week and I thought I'd post it.
Running a report I get a Crash/Error
With Error
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
In log
C:\Program Files\Windows Small Business Server\Logs\console.log
there is a "NullReferenceException"
The problem was I deleted a computer group in WSUS 3.0
I deleted the Group "Update Service Excluded Computers"
(Since I felt it didn't matter since there were no computers in that group.)
Well WRONG it does matter Make sure you have all Groups.
Unassigned Computers
Update Service Excluded Computers
Update Services Client Computers
Update Services Server Computers
Note "Update Service Excluded computer" and it should NOT be "Update
Services Excluded computer" which 'Services' is plural
If any groups are not in the list or the names are not exact same, the
report will crash.
Russ
How to restore a corrupted Windows SharePoint 3.0 Services home page
Windows SharePoint Services 3.0
Windows SharePoint Services 3.0 includes a feature that you can use to re-ghost a page. The option to re-ghost a page lets you revert to the template that does not contain any errors which is stored in the database. Follow these steps:
Start SharePoint Designer 2007.
On the File menu, click Open Site.
In the Open Site dialog box, type in the Site Name box, and then click Open.
In the Folder List dialog box, click to select, and then right-click Check-Out.
On the Edit menu, click Check-In.
Note A Green circle next to the page is displayed to indicate that the page is un-ghosted.
In the Folder List dialog box, right-click, and then click Revert to Template.
Windows SharePoint Services 3.0 includes a feature that you can use to re-ghost a page. The option to re-ghost a page lets you revert to the template that does not contain any errors which is stored in the database. Follow these steps:
Start SharePoint Designer 2007.
On the File menu, click Open Site.
In the Open Site dialog box, type
In the Folder List dialog box, click to select
On the Edit menu, click Check-In.
Note A Green circle next to the page is displayed to indicate that the page is un-ghosted.
In the Folder List dialog box, right-click
How to restore a corrupted Windows SharePoint 2.0 Services home page
Restore a corrupted Windows SharePoint Services 2.0 home page
Copy the Default.aspx file in the Windows SharePoint Services site that contains the corrupted home page, rename the copy Defaultold.aspx, and then delete the Default.aspx file. To do so, follow these steps:
Start FrontPage 2003, and then open the Windows SharePoint Services site that contains the corrupted home page.
In the Folder List, double-click the Default.aspx file.
On the File menu, click Save As.
In the Save As dialog box, type Defaultold.aspx in the File name box, and then click Save.
In the Folder List, right-click the Default.aspx file, and then click Delete.
When you are prompted to confirm the deletion, click Yes.
Create a new Windows SharePoint Services site. To do so, follow these steps:
On the File menu, click New.
In the New task pane, under New Web site, click SharePoint team site.
In the Web Site Templates dialog box, click SharePoint Team Site, and then click OK.
Under Options, type the URL of the new Windows SharePoint Services site.
For example, you can create the new site as a subsite of the site that contains the corrupted home page. If the URL of the site that contains the corrupted home page is http://ServerName/Sites/TeamSite, you can specify a URL such as http://ServerName/Sites/TeamSite/SubsiteName for your new site.
Open the new site that you created.
To do so, on the File menu, click Open Site, in the Site name box, type the URL of the new site that you created earlier in step 2, and then click Open.
In the Folder List, double-click the Default.aspx file, and then click Copy.
Change to the original site that contains the corrupted home page, right-click an empty area under the Folder List, and then click Paste.
Delete any corrupted Web Parts that are located on the Default.aspx page. To do so, follow these steps:
Connect to the home page (the Default.aspx page) of your original site in your Web browser.
Click Modify Shared Page, and then click Design this Page.
Click the down arrow next to the Web Parts that you want to delete, and then click Delete.
Click Yes when you are prompted to confirm the deletion.
Add the Web Parts that you deleted to the Default.aspx page. To do so, follow these steps:
Click Modify Shared Page, click Add Web Parts, and then click Browse.
Add the Web Parts that you want to your home page.
For example, drag the Announcements Web Part and the Events Web Part to the page.
If the Home link is missing from the top link bar, add the link to the home page back to the top link bar. To do so, follow these steps:
In FrontPage 2003, open the site (if it is not already open).
In the Folder List, double-click the Default.aspx file.
In the link bar, click add link.
In the Add to Link bar dialog box, type Home in the Text to display box, click the Default.aspx file, make sure that Default.aspx is displayed in the Address box, and then click OK.
Double-click the link bar.
In the Link Bar Properties dialog box, click the General tab, and then in the Links box, make sure that Home link appears at the top of the list.
After you finish recovering the home page, delete the Defaultold.aspx file. To do so, follow these steps:
In the Folder List, right-click the Defaultold.aspx file, and then click Delete
When you are prompted to confirm the deletion, click Yes
Copy the Default.aspx file in the Windows SharePoint Services site that contains the corrupted home page, rename the copy Defaultold.aspx, and then delete the Default.aspx file. To do so, follow these steps:
Start FrontPage 2003, and then open the Windows SharePoint Services site that contains the corrupted home page.
In the Folder List, double-click the Default.aspx file.
On the File menu, click Save As.
In the Save As dialog box, type Defaultold.aspx in the File name box, and then click Save.
In the Folder List, right-click the Default.aspx file, and then click Delete.
When you are prompted to confirm the deletion, click Yes.
Create a new Windows SharePoint Services site. To do so, follow these steps:
On the File menu, click New.
In the New task pane, under New Web site, click SharePoint team site.
In the Web Site Templates dialog box, click SharePoint Team Site, and then click OK.
Under Options, type the URL of the new Windows SharePoint Services site.
For example, you can create the new site as a subsite of the site that contains the corrupted home page. If the URL of the site that contains the corrupted home page is http://ServerName/Sites/TeamSite, you can specify a URL such as http://ServerName/Sites/TeamSite/SubsiteName for your new site.
Open the new site that you created.
To do so, on the File menu, click Open Site, in the Site name box, type the URL of the new site that you created earlier in step 2, and then click Open.
In the Folder List, double-click the Default.aspx file, and then click Copy.
Change to the original site that contains the corrupted home page, right-click an empty area under the Folder List, and then click Paste.
Delete any corrupted Web Parts that are located on the Default.aspx page. To do so, follow these steps:
Connect to the home page (the Default.aspx page) of your original site in your Web browser.
Click Modify Shared Page, and then click Design this Page.
Click the down arrow next to the Web Parts that you want to delete, and then click Delete.
Click Yes when you are prompted to confirm the deletion.
Add the Web Parts that you deleted to the Default.aspx page. To do so, follow these steps:
Click Modify Shared Page, click Add Web Parts, and then click Browse.
Add the Web Parts that you want to your home page.
For example, drag the Announcements Web Part and the Events Web Part to the page.
If the Home link is missing from the top link bar, add the link to the home page back to the top link bar. To do so, follow these steps:
In FrontPage 2003, open the site (if it is not already open).
In the Folder List, double-click the Default.aspx file.
In the link bar, click add link.
In the Add to Link bar dialog box, type Home in the Text to display box, click the Default.aspx file, make sure that Default.aspx is displayed in the Address box, and then click OK.
Double-click the link bar.
In the Link Bar Properties dialog box, click the General tab, and then in the Links box, make sure that Home link appears at the top of the list.
After you finish recovering the home page, delete the Defaultold.aspx file. To do so, follow these steps:
In the Folder List, right-click the Defaultold.aspx file, and then click Delete
When you are prompted to confirm the deletion, click Yes
Tuesday, July 14, 2009
Installing Trend Micro WFBS 6.0 Error Copying File tmplcinf.xml
Installing Trend Micro WFBS 6.0 Error Copying File tmplcinf.xml
Check to make sure file tmplcinf.xml exists in Directories.
\Program Files\Trend Micro\Security Server\PCCSRV\
\Program Files\Trend Micro\Security Server\PCCSRV\pccnt\common
\Program Files\Trend Micro\Security Server\PCCSRV\Admin
\Program Files\Trend Micro\Security Server\PCCSRV\download\pattern
If not copy it from another place and try to reinstall on the client.
Check to make sure file tmplcinf.xml exists in Directories.
\Program Files\Trend Micro\Security Server\PCCSRV\
\Program Files\Trend Micro\Security Server\PCCSRV\pccnt\common
\Program Files\Trend Micro\Security Server\PCCSRV\Admin
\Program Files\Trend Micro\Security Server\PCCSRV\download\pattern
If not copy it from another place and try to reinstall on the client.
Known issues in Worry-Free Business Security (WFBS) Standard / Advanced 6.0
For Current List Go to link:
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
From Link Above!
Published: 6/9/2009 5:34 AM
--------------------------------------
The following are known issues in WFBS Standard / Advanced 6.0:
• Client Deployment and Upgrade
o Worry-Free Business Security is unable to install CSA to a Windows Vista computer using Remote Install if the Remote Registry service is not running or if the computer does not allow File and Printer Sharing through Windows Firewall.
o When remotely installing an agent to a computer running Windows XP, disable Simple File Sharing on the target computer. Also, note that you cannot use Remote Install to deploy to a computer with Windows XP Home Edition.
o To completely reinstall or upgrade CSA, you will need to restart the computer. A restart will also be necessary when updating some components, including the firewall and the proxy drivers.
o After installing CSA on a computer with IIS 7.0, you must restart the IIS service. IIS 7.0 may not work as expected with CSA, which uses the Windows Filtering Platform, until it is restarted.
o You cannot run the Autopcc.exe, the login script, and the Client Packager from a terminal session.
o You cannot run Update Now on Windows 2000 computers from a terminal session.
o When accessing a computer with CSA from a terminal session, another unnecessary instance of the PccNTMon process is created in memory on the remote computer.
o Some CSA components, such as the Trend Micro Web Protection Add-On or the TrendProtect Desktop, can be installed without CSA. These components may conflict with the CSA installation and must be removed before CSA is installed.
o To use Trend Micro Vulnerability Scanner (TMVS) to deploy the CSA, you need to run TMVS on a computer running Windows 2000 or Windows Server 2003. TMVS does not support terminal sessions.
o Real-time scan on CSA can prevent Hyper-V Manager from creating virtual machines. If you encounter this issue, configure real-time scan to exclude the storage folder for your virtual machines from scanning. Hyper-V Manager uses "C:\ProgramData\Microsoft\Windows\Hyper-V" as the default storage folder, but a different folder may be specified during virtual machine creation.
o Installing or uninstalling the CSA on Windows 7 Build 7048 or Build 7057 will cause the Network Interface Card to get an IP address through DHCP with a 169.254 prefix, no matter the IP address is configured (static or dynamic). The NIC must be disabled first before installation to prevent this issue.
• Security Server
o The Security Server sends notifications for all triggered events whenever the Trend Micro Security Server Master Service is restarted.
o The following default Security Server and Scan Server ports must not be used or blocked by other applications, such as Microsoft ISA Server and other firewalls:
- HTTP: 8059
- SSL: 4343 and 4345
o Behavior Monitoring only blocks programs in the exact path specified in the list of blocked programs.
o No plug-in programs are currently available for versions 5.1 and 6.0.
o The Security Server installation automatically checks for Microsoft Data Access Components (MDAC) 2.6 or later. If MDAC 2.6 or later is not installed, it automatically installs MDAC 2.8.
Note: MDAC installation requires a restart.
o Update agents do not roll back to a previous pattern file, even if the Security Server rolled back to a previous version. If the agent updates its components from the Update Agent, the agent pattern file is used, not the Security Server pattern file.
o If an Internet connection problem occurs during Security Server installation, the installer will keep trying to validate the Activation Code without indicating any problem.
o Web installation and Remote installation will fail if another computer on the network has the same name as the Security Server.
• Web Console
o Trend Micro recommends accessing the Web console from computers that do not have adware installed. If Hotbar or other adware is installed, ActiveX errors may occur when accessing certain console screens.
o Trend Micro recommends setting Internet Explorer to apply Medium or lower security levels when accessing the Web console. Higher security settings may block necessary ActiveX controls.
By default, Internet Explorer applies Medium-low security levels for intranet sites and Medium security levels for sites in its Trusted Sites list. To help ensure you can access the console properly, add it to the Trusted Sites list.
• Firewall
o While installing CSA, the computer could temporarily lose network connection. Some applications, such as Secure Shell (SSH), Terminal Services Client, or Remote Desktop could be affected by the disconnection. If this occurs, restart the application after installing CSA.
o The CSA firewall might conflict with other firewall applications. Trend Micro recommends uninstalling or disabling the other firewall applications.
o On VMWare clients, the CSA firewall may block all incoming packets. To address this issue, add the following value to the client's registry:
- Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW
- Name: EnableBypassRule
- Type: REG_DWORD
- Data: 1
• Transaction Protector
o After Transaction Protector scans a wireless access point, it shows the "unchecked" status if a timeout occurs while trying to connect to the access point.
o Transaction Protector only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
o Transaction Protector does not support remote administration software, such as Remote Desktop.
• TrendProtect
o TrendProtect cannot start automatically when installed for the first time on a computer with Internet Explorer 7.0 and Windows XP. To manually enable TrendProtect, go to View > Toolbars > TrendProtect in the Internet Explorer menu.
o TrendProtect only supports:
- Windows 2000 Professional
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Behavior Monitoring
o Behavior Monitoring only supports 32-bit operating systems; 64-bit operating systems are not supported.
o Files without valid digital signatures that violate policies may be blocked by Behavior Monitoring. Files with valid signatures are always allowed to start.
• Trend Micro Anti-Spam Toolbar
o The Trend Micro Anti-Spam Toolbar only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Messaging Security Agent
o The Messaging Security Agent (MSA) only supports typical installations of Exchange Server 2007 that include the Hub Transport, the Mailbox, and the Client Access server roles.
o As an anti-spam solution on Exchange Server 2003, users can choose between EUQ or Junk Mail integration. If you use Junk Mail integration, install Exchange Server 2003 SP2, which includes the Intelligent Message Filter (IMF), before installing MSA.
o During MSA installation, the installer may be unable to submit passwords that have special, non-alphanumeric characters to the Exchange Server computer. As a result, you may be unable to install the MSA if the domain administrator account you are using has a complex password. To work around this issue, temporarily change the password for the domain administrator account.
o When installing MSA remotely using the Web console or the Worry-Free Business Security Advanced installer to a computer running Windows Server 2008, SBS 2008, or EBS 2008, you need to specify the built-in domain administrator account because of User Access Control restrictions. Note that for computers with other operating systems, you need an account that is in the Exchange Organization Administrators group.
o During MSA installation, the setup program adds a Windows Firewall exception on the Exchange Server computer to allow the MSA to communicate with the Security Server through port 16372.
o The MSA cannot be installed on a Windows EBS 2008 computer with the Exchange Server 2007 Edge Transport server role.
• Email Reputation Services
o Email Reputation Services (ERS) is an online hosted service and its activation takes about eight hours.
http://esupport.trendmicro.com/Pages/Known-issues-in-Worry-Free-Business-Security-(WFBS)-Standard--Advanced-60.aspx
From Link Above!
Published: 6/9/2009 5:34 AM
--------------------------------------
The following are known issues in WFBS Standard / Advanced 6.0:
• Client Deployment and Upgrade
o Worry-Free Business Security is unable to install CSA to a Windows Vista computer using Remote Install if the Remote Registry service is not running or if the computer does not allow File and Printer Sharing through Windows Firewall.
o When remotely installing an agent to a computer running Windows XP, disable Simple File Sharing on the target computer. Also, note that you cannot use Remote Install to deploy to a computer with Windows XP Home Edition.
o To completely reinstall or upgrade CSA, you will need to restart the computer. A restart will also be necessary when updating some components, including the firewall and the proxy drivers.
o After installing CSA on a computer with IIS 7.0, you must restart the IIS service. IIS 7.0 may not work as expected with CSA, which uses the Windows Filtering Platform, until it is restarted.
o You cannot run the Autopcc.exe, the login script, and the Client Packager from a terminal session.
o You cannot run Update Now on Windows 2000 computers from a terminal session.
o When accessing a computer with CSA from a terminal session, another unnecessary instance of the PccNTMon process is created in memory on the remote computer.
o Some CSA components, such as the Trend Micro Web Protection Add-On or the TrendProtect Desktop, can be installed without CSA. These components may conflict with the CSA installation and must be removed before CSA is installed.
o To use Trend Micro Vulnerability Scanner (TMVS) to deploy the CSA, you need to run TMVS on a computer running Windows 2000 or Windows Server 2003. TMVS does not support terminal sessions.
o Real-time scan on CSA can prevent Hyper-V Manager from creating virtual machines. If you encounter this issue, configure real-time scan to exclude the storage folder for your virtual machines from scanning. Hyper-V Manager uses "C:\ProgramData\Microsoft\Windows\Hyper-V" as the default storage folder, but a different folder may be specified during virtual machine creation.
o Installing or uninstalling the CSA on Windows 7 Build 7048 or Build 7057 will cause the Network Interface Card to get an IP address through DHCP with a 169.254 prefix, no matter the IP address is configured (static or dynamic). The NIC must be disabled first before installation to prevent this issue.
• Security Server
o The Security Server sends notifications for all triggered events whenever the Trend Micro Security Server Master Service is restarted.
o The following default Security Server and Scan Server ports must not be used or blocked by other applications, such as Microsoft ISA Server and other firewalls:
- HTTP: 8059
- SSL: 4343 and 4345
o Behavior Monitoring only blocks programs in the exact path specified in the list of blocked programs.
o No plug-in programs are currently available for versions 5.1 and 6.0.
o The Security Server installation automatically checks for Microsoft Data Access Components (MDAC) 2.6 or later. If MDAC 2.6 or later is not installed, it automatically installs MDAC 2.8.
Note: MDAC installation requires a restart.
o Update agents do not roll back to a previous pattern file, even if the Security Server rolled back to a previous version. If the agent updates its components from the Update Agent, the agent pattern file is used, not the Security Server pattern file.
o If an Internet connection problem occurs during Security Server installation, the installer will keep trying to validate the Activation Code without indicating any problem.
o Web installation and Remote installation will fail if another computer on the network has the same name as the Security Server.
• Web Console
o Trend Micro recommends accessing the Web console from computers that do not have adware installed. If Hotbar or other adware is installed, ActiveX errors may occur when accessing certain console screens.
o Trend Micro recommends setting Internet Explorer to apply Medium or lower security levels when accessing the Web console. Higher security settings may block necessary ActiveX controls.
By default, Internet Explorer applies Medium-low security levels for intranet sites and Medium security levels for sites in its Trusted Sites list. To help ensure you can access the console properly, add it to the Trusted Sites list.
• Firewall
o While installing CSA, the computer could temporarily lose network connection. Some applications, such as Secure Shell (SSH), Terminal Services Client, or Remote Desktop could be affected by the disconnection. If this occurs, restart the application after installing CSA.
o The CSA firewall might conflict with other firewall applications. Trend Micro recommends uninstalling or disabling the other firewall applications.
o On VMWare clients, the CSA firewall may block all incoming packets. To address this issue, add the following value to the client's registry:
- Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW
- Name: EnableBypassRule
- Type: REG_DWORD
- Data: 1
• Transaction Protector
o After Transaction Protector scans a wireless access point, it shows the "unchecked" status if a timeout occurs while trying to connect to the access point.
o Transaction Protector only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
o Transaction Protector does not support remote administration software, such as Remote Desktop.
• TrendProtect
o TrendProtect cannot start automatically when installed for the first time on a computer with Internet Explorer 7.0 and Windows XP. To manually enable TrendProtect, go to View > Toolbars > TrendProtect in the Internet Explorer menu.
o TrendProtect only supports:
- Windows 2000 Professional
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Behavior Monitoring
o Behavior Monitoring only supports 32-bit operating systems; 64-bit operating systems are not supported.
o Files without valid digital signatures that violate policies may be blocked by Behavior Monitoring. Files with valid signatures are always allowed to start.
• Trend Micro Anti-Spam Toolbar
o The Trend Micro Anti-Spam Toolbar only supports:
- Windows XP SP2 32-bit
- Windows Vista and Vista SP1 (32-bit and 64-bit)
• Messaging Security Agent
o The Messaging Security Agent (MSA) only supports typical installations of Exchange Server 2007 that include the Hub Transport, the Mailbox, and the Client Access server roles.
o As an anti-spam solution on Exchange Server 2003, users can choose between EUQ or Junk Mail integration. If you use Junk Mail integration, install Exchange Server 2003 SP2, which includes the Intelligent Message Filter (IMF), before installing MSA.
o During MSA installation, the installer may be unable to submit passwords that have special, non-alphanumeric characters to the Exchange Server computer. As a result, you may be unable to install the MSA if the domain administrator account you are using has a complex password. To work around this issue, temporarily change the password for the domain administrator account.
o When installing MSA remotely using the Web console or the Worry-Free Business Security Advanced installer to a computer running Windows Server 2008, SBS 2008, or EBS 2008, you need to specify the built-in domain administrator account because of User Access Control restrictions. Note that for computers with other operating systems, you need an account that is in the Exchange Organization Administrators group.
o During MSA installation, the setup program adds a Windows Firewall exception on the Exchange Server computer to allow the MSA to communicate with the Security Server through port 16372.
o The MSA cannot be installed on a Windows EBS 2008 computer with the Exchange Server 2007 Edge Transport server role.
• Email Reputation Services
o Email Reputation Services (ERS) is an online hosted service and its activation takes about eight hours.
Sunday, June 28, 2009
To uninstall and reinstall sharepoint 3.0 on SBS2008
To uninstall sharepoint 3.0 on SBS2008, please follow these steps:
======
Step 1: Uninstall WSS3.0:
======
Disable and Stop the following services
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer
Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
-InstallPath (default is C:\Program Files\Microsoft Office Servers\12)
From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
Delete the following registry hives:
HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WSS
Delete the following folders:
The value of the InstallPath key (default is C:\Program Files\Microsoft Office Servers\12)
The value of the Location key (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12
Step 2: use Windows Installer cleanup:
======
This utility is to clean the product code information:
1. please download and install installer cleanup utility from this link:
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301
2. please run these commands after you have installed the utility:
Cd c:\program files(x86)\windows installer clean up\
MSIZAP TW {90120000-1015-0409-0000-0000000FF1CE}
MSIZAP TW {90120000-1014-0000-0000-0000000FF1CE}
MSIZAP TW {90120000-1110-0000-0000-0000000FF1CE}
3. please reboot server.
Step 3: reinstall Sharepoint 3.0:
======
1. save the following into notepad, and then save as a REG file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\ServerLanguage]
"1033"=""
2. double click the REG file to import the registry.
3. Please reinstall sharepoint 3.0 according to this link:
Reinstall Windows SharePoint Services
http://technet.microsoft.com/en-us/library/dd548327(WS.10).aspx
======
Step 1: Uninstall WSS3.0:
======
Disable and Stop the following services
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer
Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
-InstallPath (default is C:\Program Files\Microsoft Office Servers\12)
From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
Delete the following registry hives:
HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WSS
Delete the following folders:
The value of the InstallPath key (default is C:\Program Files\Microsoft Office Servers\12)
The value of the Location key (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12
Step 2: use Windows Installer cleanup:
======
This utility is to clean the product code information:
1. please download and install installer cleanup utility from this link:
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301
2. please run these commands after you have installed the utility:
Cd c:\program files(x86)\windows installer clean up\
MSIZAP TW {90120000-1015-0409-0000-0000000FF1CE}
MSIZAP TW {90120000-1014-0000-0000-0000000FF1CE}
MSIZAP TW {90120000-1110-0000-0000-0000000FF1CE}
3. please reboot server.
Step 3: reinstall Sharepoint 3.0:
======
1. save the following into notepad, and then save as a REG file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\ServerLanguage]
"1033"=""
2. double click the REG file to import the registry.
3. Please reinstall sharepoint 3.0 according to this link:
Reinstall Windows SharePoint Services
http://technet.microsoft.com/en-us/library/dd548327(WS.10).aspx
Friday, June 19, 2009
Where Can I get the Microsoft Font?
I'm unsure of the license with this?
But like me when you want to use the word "Microsoft" in your Documents and you want it to look just as Cool as Microsoft does.
(Especially when you write sales flyers for the clients)
You need the Font.
The font is: Helvetica 96 Black Italic.ttf
and can be downloaded here.
http://www.sbits.biz/MicrosoftFont/
Downloaded it to your Font directory
%windir%\fonts (AKA C:\Windows\Fonts\)
and next reboot you have them.
No Warranties with this file, use at your own risk!
But like me when you want to use the word "Microsoft" in your Documents and you want it to look just as Cool as Microsoft does.
(Especially when you write sales flyers for the clients)
You need the Font.
The font is: Helvetica 96 Black Italic.ttf
and can be downloaded here.
http://www.sbits.biz/MicrosoftFont/
Downloaded it to your Font directory
%windir%\fonts (AKA C:\Windows\Fonts\)
and next reboot you have them.
No Warranties with this file, use at your own risk!
Thursday, June 18, 2009
How to Change the CompanyWeb Timeout in SBS 2008
The CompanyWeb site in SBS 2008 is configured with a 30 minute idle timeout in the default master page. This timeout is unique to CompanyWeb in SBS 2008 and affects connections to CompanyWeb from the LAN or over the Internet. To change this timeout:
1.Create a backup of your current CompanyWeb using the native SBS backup.
2.Browse to http://companyweb.
3.Click Site Actions and then click Site Settings.
4.In the Galleries section, click Master pages.
5.Right-click default.master, point to Send To and then click Download a copy. Save the file in the My Documents or some folder of your choosing.
6.Make a backup copy of this file.
7.Open the default.master file in Notepad.
8.Locate this section:
//this value indicates after how many miliseconds
var LOGIN_SESSION_TIMEOUT_VALUE = 1800000;
function EndSession()
{
window.location = "/_layouts/SignOut.aspx";
}
9.Modify the 1800000 value to the desired timeout in milliseconds.
60000 milliseconds = 1 minute
1800000 milliseconds = 30 minutes (default)
3600000 milliseconds = 1 hour
10.In Notepad, click File and then click Save. The file should be saved as default.master and not default.master.txt. Note the MASTER File type in the screenshot below.
11.In CompanyWeb, click Upload, and select the default.master file. Leave the box Add as a new version to existing files checked and click OK. You can also specify the change you made in the comments section.
12.After the document is uploaded, click OK.
Note: It should appear in the master page gallery default.master and not default.master.txt (or any other extension).
1.Create a backup of your current CompanyWeb using the native SBS backup.
2.Browse to http://companyweb.
3.Click Site Actions and then click Site Settings.
4.In the Galleries section, click Master pages.
5.Right-click default.master, point to Send To and then click Download a copy. Save the file in the My Documents or some folder of your choosing.
6.Make a backup copy of this file.
7.Open the default.master file in Notepad.
8.Locate this section:
//this value indicates after how many miliseconds
var LOGIN_SESSION_TIMEOUT_VALUE = 1800000;
function EndSession()
{
window.location = "/_layouts/SignOut.aspx";
}
9.Modify the 1800000 value to the desired timeout in milliseconds.
60000 milliseconds = 1 minute
1800000 milliseconds = 30 minutes (default)
3600000 milliseconds = 1 hour
10.In Notepad, click File and then click Save. The file should be saved as default.master and not default.master.txt. Note the MASTER File type in the screenshot below.
11.In CompanyWeb, click Upload, and select the default.master file. Leave the box Add as a new version to existing files checked and click OK. You can also specify the change you made in the comments section.
12.After the document is uploaded, click OK.
Note: It should appear in the master page gallery default.master and not default.master.txt (or any other extension).
Sunday, May 31, 2009
How to Enable OOF (out of office assistant) in SBS2008 to send outside the domain
Open up Exchange Management Console
Expand Organization Configuration
Right Click on "Hub Transport"
Click TAB "Remote Domains"
Right click on Default (And Select Properties)
In the General TAB (Default)
you will see those options for OOF
Expand Organization Configuration
Right Click on "Hub Transport"
Click TAB "Remote Domains"
Right click on Default (And Select Properties)
In the General TAB (Default)
you will see those options for OOF
Wednesday, May 27, 2009
Where is the Show Desktop icon in Windows 7
The Show Desktop icon in Windows 7 is located on the far right of the toolbar
(Just right of the toolbar Clock)
(Just right of the toolbar Clock)
How to Reinstall SharePoint 3.0 on SBS2008
To uninstall sharepoint 3.0 on SBS2008, please follow these steps:
======
Step 1: Uninstall WSS3.0:
======
Disable and Stop the following services
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer
Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
-InstallPath (default is C:\Program Files\Microsoft Office Servers\12)
From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
Delete the following registry hives:
HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WSS
Delete the following folders:
The value of the InstallPath key (default is C:\Program Files\Microsoft Office Servers\12)
The value of the Location key (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12
Step 2: use Windows Installer cleanup:
======
This utility is to clean the product code information:
1. please download and install installer cleanup utility from this link:
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301
2. please run these commands after you have installed the utility:
Cd c:\program files(x86)\windows installer clean up\
MSIZAP TW {90120000-1015-0409-0000-0000000FF1CE}
MSIZAP TW {90120000-1014-0000-0000-0000000FF1CE}
MSIZAP TW {90120000-1110-0000-0000-0000000FF1CE}
3. please reboot server.
Step 3: reinstall Sharepoint 3.0:
======
1. save the following into notepad, and then save as a REG file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\ServerLanguage]
"1033"=""
2. double click the REG file to import the registry.
3. Reinstall sharepoint 3.0 according to this link:
Reinstall Windows SharePoint Services
http://technet.microsoft.com/en-us/library/dd548327(WS.10).aspx
======
Step 1: Uninstall WSS3.0:
======
Disable and Stop the following services
-Windows SharePoint Services Administration
-Windows SharePoint Services Search
-Windows SharePoint Services Timer
-Windows SharePoint Services Tracing
-Windows SharePoint Services VSS Writer
Note the following registry keys:
From HKLM\Software\Microsoft\Office Server\12.0
-InstallPath (default is C:\Program Files\Microsoft Office Servers\12)
From HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
-Location (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
Delete the following registry hives:
HKLM\Software\Microsoft\Shared Tools\Web Server Extensions\12.0
HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\WSS
Delete the following folders:
The value of the InstallPath key (default is C:\Program Files\Microsoft Office Servers\12)
The value of the Location key (default is C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12)
C:\%CommonProgramFiles%\Microsoft Shared\SERVER12
Step 2: use Windows Installer cleanup:
======
This utility is to clean the product code information:
1. please download and install installer cleanup utility from this link:
Description of the Windows Installer CleanUp Utility
http://support.microsoft.com/kb/290301
2. please run these commands after you have installed the utility:
Cd c:\program files(x86)\windows installer clean up\
MSIZAP TW {90120000-1015-0409-0000-0000000FF1CE}
MSIZAP TW {90120000-1014-0000-0000-0000000FF1CE}
MSIZAP TW {90120000-1110-0000-0000-0000000FF1CE}
3. please reboot server.
Step 3: reinstall Sharepoint 3.0:
======
1. save the following into notepad, and then save as a REG file.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\ServerLanguage]
"1033"=""
2. double click the REG file to import the registry.
3. Reinstall sharepoint 3.0 according to this link:
Reinstall Windows SharePoint Services
http://technet.microsoft.com/en-us/library/dd548327(WS.10).aspx
Monday, May 25, 2009
Where the Heck is Telnet in Windows 7?
Just like Vista Telnet is disabled by default in Windows 7
To Enable it:
•open control panel
•Then go into programs
•Then in programs and features there should be a part that says ‘turn windows features on or off ‘
•Click ‘turn windows features on or off ‘ then on the list that appears simply choose: Telnet Client
After waiting your Much needed Tool Telnet is back :)
Russ
To Enable it:
•open control panel
•Then go into programs
•Then in programs and features there should be a part that says ‘turn windows features on or off ‘
•Click ‘turn windows features on or off ‘ then on the list that appears simply choose: Telnet Client
After waiting your Much needed Tool Telnet is back :)
Russ
Wednesday, May 13, 2009
Uninstall WSUS 3.0 SP1
RE: Uninstall WSUS 3.0 SP1
If you cannot uninstall WSUS 3.0 SP1 through "Add/Remove Programs", please
try the following steps to manually remove it:
1. Download the SDK to obtain MSIZAP
http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d
5e1bd/msicuu2.exe
2. From a command prompt, type:
MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type:
MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. From a command prompt, type: iisreset
The MSIZAP switch "T" removes all info for given product code
6. Run the following command to delete Windows Internal Database:
msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
7. Delete WSUS folder C:\Program Files\Update Services
8. Open IIS manager, delete all WSUS related virtual directory:
ApiRemoting30
ClientWebService
Content
DssAuthWebService
Inventory
ReportingWebService
Selfupdate
ServerSyncWebService
SimpleAuthWebService
If you cannot uninstall WSUS 3.0 SP1 through "Add/Remove Programs", please
try the following steps to manually remove it:
1. Download the SDK to obtain MSIZAP
http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d
5e1bd/msicuu2.exe
2. From a command prompt, type:
MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
3. From a command prompt, type: sc delete wsusservice
4. Again, From a command prompt, type:
MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}
5. From a command prompt, type: iisreset
The MSIZAP switch "T" removes all info for given product code
6. Run the following command to delete Windows Internal Database:
msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
7. Delete WSUS folder C:\Program Files\Update Services
8. Open IIS manager, delete all WSUS related virtual directory:
ApiRemoting30
ClientWebService
Content
DssAuthWebService
Inventory
ReportingWebService
Selfupdate
ServerSyncWebService
SimpleAuthWebService
Monday, May 04, 2009
After Migration SBS2008 Computers not showing up in Console?
Q: Why are some of my computers not showing up in the Administration Console?
A: The most likely cause is that the computer object is not present in the correct organizational unit (OU) in active directory. The SBS console will only display computers that are present in the \Domain Controllers, \MyBusiness\Computers\SBSServers, and \MyBusiness\Computers\SBSComputers OUs.
Due to the way SBS 2008 manages the domain, it is imperative that the objects are in the correct locations. Otherwise SBS 2008 will not display them as there is no assurance the objects can be configured properly. By default, new computers appear in \MyBusiness\Computers\SBSComputers.
Move the objects to the correct group and they should show up.
A: The most likely cause is that the computer object is not present in the correct organizational unit (OU) in active directory. The SBS console will only display computers that are present in the \Domain Controllers, \MyBusiness\Computers\SBSServers, and \MyBusiness\Computers\SBSComputers OUs.
Due to the way SBS 2008 manages the domain, it is imperative that the objects are in the correct locations. Otherwise SBS 2008 will not display them as there is no assurance the objects can be configured properly. By default, new computers appear in \MyBusiness\Computers\SBSComputers.
Move the objects to the correct group and they should show up.
Wednesday, April 29, 2009
Exchange connection filter using a Real Time Block list, and IMFPerfmon.msc - Buckeye Gone Bad - MSMVPS.COM
Exchange connection filter using a Real Time Block list, and IMFPerfmon.msc -
IMFPerfmon.msc
Posted By Buckeye Gone Bad
Here are some things I do. I may miss a step so you may have to
confirm things. After you added connection filter provider you need to
make sure you have checked that stuff in the default virtual server.
Global Settings/Message Delivery right click Properties.
Sender Filtering: Check Filter messages with a blank sender and Drop
connection if address filter matches filter.
Connection Filtering: Add your favorite RBL services. I happen to use zen.spamhaus.org Please visit www.spamhaus.org to review terms and conditions to see if you are eligible to use their services.
Intelligent Messaging Filtering: I set it at 7 and Reject. You want
reject so if there was a valid message the sender receives notice that
your server rejected the message.
Recipient Filtering: Filter recipients who are not in the Directory.
Apply and go to Servers/Servername/Protocols/Default SMTP Virtual
Server right click Properties.
Advanced.
Edit
I check everything but Sender ID Filter.
Make sure you are on Exchange SP2 and you add the registry dword
HKLM\Software\Microsoft\Exchange\ ContentFilterState set to 1. That
key lets Microsoft Updates get IMF definitions.
I open up perfmon.msc from the Run box.
On the icon bar I click on the notebook icon to get the report view.
Click on the + sign next to it to add some counters.
In the Performance Object drop down box look for
MSExchange Transport Filter Sink. Choose all counters and Add.
Back to Performance Object and choose MSExchange Intelligent Message
Filter. Choose all counters and Add. I really do not care for the per
second counters so you can choose select counters from list if you
like.
Now you have a permon that is showing how much stuff is going in to
your Exchange server that the IMF considers spam. It shows you how
many connections are being rejected by the RBL. It shows you how many
connections are being dropped because the recipient is not in your
Active Directory. I do a little math and come up with some interesting
numbers.
Click on File and save as. I save it as imfperfmon.msc. I right click
on the desktop and make a new shortcut. Type imfperfmon.msc in the
next two boxes. Now you have a shortcut on your desktop anytime you
want to see how the RBL and IMF are doing.
Back to your question. If you have the imfperfmon working you can see
a little about what is coming in. Last night I had an account getting
slammed with some mailer daemon nonsense. I need to visit to see what
is really going on.
Mail may still be stuck in the queue as your server is trying to send
out Non Delivery Reports to bogus addresses. If you have done the
clicks I mentioned and others hopefully the junk will be blocked.
Those NDRs will die off after a few days. The default setting in
Exchange is to try to deliver for 2 days and then give up. There is a
trick to flush all the messages out but it may be just as easy to let
them die out on their own. As long as you do the clicks I did you
should eventually be ok.
IMFPerfmon.msc
Posted By Buckeye Gone Bad
Here are some things I do. I may miss a step so you may have to
confirm things. After you added connection filter provider you need to
make sure you have checked that stuff in the default virtual server.
Global Settings/Message Delivery right click Properties.
Sender Filtering: Check Filter messages with a blank sender and Drop
connection if address filter matches filter.
Connection Filtering: Add your favorite RBL services. I happen to use zen.spamhaus.org Please visit www.spamhaus.org to review terms and conditions to see if you are eligible to use their services.
Intelligent Messaging Filtering: I set it at 7 and Reject. You want
reject so if there was a valid message the sender receives notice that
your server rejected the message.
Recipient Filtering: Filter recipients who are not in the Directory.
Apply and go to Servers/Servername/Protocols/Default SMTP Virtual
Server right click Properties.
Advanced.
Edit
I check everything but Sender ID Filter.
Make sure you are on Exchange SP2 and you add the registry dword
HKLM\Software\Microsoft\Exchange\ ContentFilterState set to 1. That
key lets Microsoft Updates get IMF definitions.
I open up perfmon.msc from the Run box.
On the icon bar I click on the notebook icon to get the report view.
Click on the + sign next to it to add some counters.
In the Performance Object drop down box look for
MSExchange Transport Filter Sink. Choose all counters and Add.
Back to Performance Object and choose MSExchange Intelligent Message
Filter. Choose all counters and Add. I really do not care for the per
second counters so you can choose select counters from list if you
like.
Now you have a permon that is showing how much stuff is going in to
your Exchange server that the IMF considers spam. It shows you how
many connections are being rejected by the RBL. It shows you how many
connections are being dropped because the recipient is not in your
Active Directory. I do a little math and come up with some interesting
numbers.
Click on File and save as. I save it as imfperfmon.msc. I right click
on the desktop and make a new shortcut. Type imfperfmon.msc in the
next two boxes. Now you have a shortcut on your desktop anytime you
want to see how the RBL and IMF are doing.
Back to your question. If you have the imfperfmon working you can see
a little about what is coming in. Last night I had an account getting
slammed with some mailer daemon nonsense. I need to visit to see what
is really going on.
Mail may still be stuck in the queue as your server is trying to send
out Non Delivery Reports to bogus addresses. If you have done the
clicks I mentioned and others hopefully the junk will be blocked.
Those NDRs will die off after a few days. The default setting in
Exchange is to try to deliver for 2 days and then give up. There is a
trick to flush all the messages out but it may be just as easy to let
them die out on their own. As long as you do the clicks I did you
should eventually be ok.
Thursday, April 23, 2009
Windows RUN Command Shortcuts
Windows RUN Command Shortcuts
RUN command shortcuts
———————————-
Accessibility Controls: access.cpl
Add Hardware Wizard: hdwwiz.cpl
Add/Remove Programs: appwiz.cpl
Administrative Tools: control admintools
Automatic Updates: wuaucpl.cpl
Bluetooth Transfer Wizard: fsquirt
Calculator: calc
Certificate Manager: certmgr.msc
Character Map: charmap
Check Disk Utility: chkdsk
Clipboard Viewer: clipbrd
Command Prompt: cmd
Component Services: dcomcnfg
Computer Management: compmgmt.msc
Date and Time Properties: timedate.cpl
DDE Shares: ddeshare
Device Manager: devmgmt.msc
Direct X Control Panel (If Installed)*: directx.cpl
Direct X Troubleshooter: dxdiag
Disk Cleanup Utility: cleanmgr
Disk Defragment: dfrg.msc
Disk Management: diskmgmt.msc
Disk Partition Manager: diskpart
Display Properties: control desktop
Display Properties: desk.cpl
Display Properties (w/Appearance Tab Preselected): control color
Dr. Watson System Troubleshooting Utility: drwtsn32
Driver Verifier Utility: verifier
Event Viewer: eventvwr.msc
File Signature Verification Tool: sigverif
Findfast: findfast.cpl
Folders Properties: control folders
Fonts: control fonts
Fonts Folder: fonts
Free Cell Card Game: freecell
Game Controllers: joy.cpl
Group Policy Editor (XP Prof): gpedit.msc
Hearts Card Game: mshearts
Iexpress Wizard: iexpress
Indexing Service: ciadv.msc
Internet Properties: inetcpl.cpl
IP Configuration (Display Connection Configuration): ipconfig /all
IP Configuration (Display DNS Cache Contents): ipconfig /displaydns
IP Configuration (Delete DNS Cache Contents): ipconfig /flushdns
IP Configuration (Release All Connections): ipconfig /release
IP Configuration (Renew All Connections): ipconfig /renew
IP Configuration (Refreshes DHCP & Re-Registers DNS): ipconfig /registerdns
IP Configuration (Display DHCP Class ID): ipconfig /showclassid
IP Configuration (Modifies DHCP Class ID): ipconfig /setclassid
Java Control Panel (If Installed): jpicpl32.cpl
Java Control Panel (If Installed): javaws
Keyboard Properties: control keyboard
Local Security Settings: secpol.msc
Local Users and Groups: lusrmgr.msc
Logs You Out Of Windows: logoff
Microsoft Chat: winchat
Minesweeper Game: winmine
Mouse Properties: control mouse
Mouse Properties: main.cpl
Network Connections: control netconnections
Network Connections: ncpa.cpl
Network Setup Wizard: netsetup.cpl
Notepad: notepad
Nview Desktop Manager (If Installed): nvtuicpl.cpl
Object Packager: packager
ODBC Data Source Administrator: odbccp32.cpl
On Screen Keyboard: osk
Opens AC3 Filter (If Installed): ac3filter.cpl
Password Properties: password.cpl
Performance Monitor: perfmon.msc
Performance Monitor: perfmon
Phone and Modem Options: telephon.cpl
Power Configuration: powercfg.cpl
Printers and Faxes: control printers
Printers Folder: printers
Private Character Editor: eudcedit
Quicktime (If Installed): QuickTime.cpl
Regional Settings: intl.cpl
Registry Editor: regedit
Registry Editor: regedit32
Remote Desktop: mstsc
Removable Storage: ntmsmgr.msc
Removable Storage Operator Requests: ntmsoprq.msc
Resultant Set of Policy (XP Prof): rsop.msc
Scanners and Cameras: sticpl.cpl
Scheduled Tasks: control schedtasks
Security Center: wscui.cpl
Services: services.msc
Shared Folders: fsmgmt.msc
Shuts Down Windows: shutdown
Sounds and Audio: mmsys.cpl
Spider Solitare Card Game: spider
SQL Client Configuration: cliconfg
System Configuration Editor: sysedit
System Configuration Utility: msconfig
System File Checker Utility (Scan Immediately): sfc /scannow
System File Checker Utility (Scan Once At Next Boot): sfc /scanonce
System File Checker Utility (Scan On Every Boot): sfc /scanboot
System File Checker Utility (Return to Default Setting): sfc /revert
System File Checker Utility (Purge File Cache): sfc /purgecache
System File Checker Utility (Set Cache Size to size x): sfc /cachesize=x
System Properties: sysdm.cpl
Task Manager: taskmgr
Telnet Client: telnet
Terminal Server Confing: tsconfig.msc
User Account Management: nusrmgr.cpl
Utility Manager: utilman
Windows Firewall: firewall.cpl
Windows Magnifier: magnify
Windows Management Infrastructure: wmimgmt.msc
Windows System Security Tool: syskey
Windows Update Launches: wupdmgr
Windows XP Tour Wizard: tourstart
Wordpad: write
RUN command shortcuts
———————————-
Accessibility Controls: access.cpl
Add Hardware Wizard: hdwwiz.cpl
Add/Remove Programs: appwiz.cpl
Administrative Tools: control admintools
Automatic Updates: wuaucpl.cpl
Bluetooth Transfer Wizard: fsquirt
Calculator: calc
Certificate Manager: certmgr.msc
Character Map: charmap
Check Disk Utility: chkdsk
Clipboard Viewer: clipbrd
Command Prompt: cmd
Component Services: dcomcnfg
Computer Management: compmgmt.msc
Date and Time Properties: timedate.cpl
DDE Shares: ddeshare
Device Manager: devmgmt.msc
Direct X Control Panel (If Installed)*: directx.cpl
Direct X Troubleshooter: dxdiag
Disk Cleanup Utility: cleanmgr
Disk Defragment: dfrg.msc
Disk Management: diskmgmt.msc
Disk Partition Manager: diskpart
Display Properties: control desktop
Display Properties: desk.cpl
Display Properties (w/Appearance Tab Preselected): control color
Dr. Watson System Troubleshooting Utility: drwtsn32
Driver Verifier Utility: verifier
Event Viewer: eventvwr.msc
File Signature Verification Tool: sigverif
Findfast: findfast.cpl
Folders Properties: control folders
Fonts: control fonts
Fonts Folder: fonts
Free Cell Card Game: freecell
Game Controllers: joy.cpl
Group Policy Editor (XP Prof): gpedit.msc
Hearts Card Game: mshearts
Iexpress Wizard: iexpress
Indexing Service: ciadv.msc
Internet Properties: inetcpl.cpl
IP Configuration (Display Connection Configuration): ipconfig /all
IP Configuration (Display DNS Cache Contents): ipconfig /displaydns
IP Configuration (Delete DNS Cache Contents): ipconfig /flushdns
IP Configuration (Release All Connections): ipconfig /release
IP Configuration (Renew All Connections): ipconfig /renew
IP Configuration (Refreshes DHCP & Re-Registers DNS): ipconfig /registerdns
IP Configuration (Display DHCP Class ID): ipconfig /showclassid
IP Configuration (Modifies DHCP Class ID): ipconfig /setclassid
Java Control Panel (If Installed): jpicpl32.cpl
Java Control Panel (If Installed): javaws
Keyboard Properties: control keyboard
Local Security Settings: secpol.msc
Local Users and Groups: lusrmgr.msc
Logs You Out Of Windows: logoff
Microsoft Chat: winchat
Minesweeper Game: winmine
Mouse Properties: control mouse
Mouse Properties: main.cpl
Network Connections: control netconnections
Network Connections: ncpa.cpl
Network Setup Wizard: netsetup.cpl
Notepad: notepad
Nview Desktop Manager (If Installed): nvtuicpl.cpl
Object Packager: packager
ODBC Data Source Administrator: odbccp32.cpl
On Screen Keyboard: osk
Opens AC3 Filter (If Installed): ac3filter.cpl
Password Properties: password.cpl
Performance Monitor: perfmon.msc
Performance Monitor: perfmon
Phone and Modem Options: telephon.cpl
Power Configuration: powercfg.cpl
Printers and Faxes: control printers
Printers Folder: printers
Private Character Editor: eudcedit
Quicktime (If Installed): QuickTime.cpl
Regional Settings: intl.cpl
Registry Editor: regedit
Registry Editor: regedit32
Remote Desktop: mstsc
Removable Storage: ntmsmgr.msc
Removable Storage Operator Requests: ntmsoprq.msc
Resultant Set of Policy (XP Prof): rsop.msc
Scanners and Cameras: sticpl.cpl
Scheduled Tasks: control schedtasks
Security Center: wscui.cpl
Services: services.msc
Shared Folders: fsmgmt.msc
Shuts Down Windows: shutdown
Sounds and Audio: mmsys.cpl
Spider Solitare Card Game: spider
SQL Client Configuration: cliconfg
System Configuration Editor: sysedit
System Configuration Utility: msconfig
System File Checker Utility (Scan Immediately): sfc /scannow
System File Checker Utility (Scan Once At Next Boot): sfc /scanonce
System File Checker Utility (Scan On Every Boot): sfc /scanboot
System File Checker Utility (Return to Default Setting): sfc /revert
System File Checker Utility (Purge File Cache): sfc /purgecache
System File Checker Utility (Set Cache Size to size x): sfc /cachesize=x
System Properties: sysdm.cpl
Task Manager: taskmgr
Telnet Client: telnet
Terminal Server Confing: tsconfig.msc
User Account Management: nusrmgr.cpl
Utility Manager: utilman
Windows Firewall: firewall.cpl
Windows Magnifier: magnify
Windows Management Infrastructure: wmimgmt.msc
Windows System Security Tool: syskey
Windows Update Launches: wupdmgr
Windows XP Tour Wizard: tourstart
Wordpad: write
Sunday, April 12, 2009
Description of the Windows Installer CleanUp Utility
Description of the Windows Installer CleanUp Utility
The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs
The Windows Installer CleanUp Utility is provided "as is" to help resolve installation problems for programs that use Microsoft Windows Installer. If you use this utility, you may have to reinstall other programs
Saturday, April 11, 2009
Friday, April 10, 2009
How to remove and how to install the Windows Small Business Server 2003 SharePoint Services 2.0 companyweb Web site
Thursday, April 09, 2009
The Official SBS Blog : System State Backups and SBS 2008
The Official SBS Blog : System State Backups and SBS 2008: "Wbadmin start systemstatebackup –backuptarget:F:"
System State Backups and SBS 2008
[Today's post comes to us courtesy of John Bay]
The normal backup that SBS 2008 creates contains all the necessary information to restore the entire server. The normal SBS backup includes the system state data. You may wish to create a system state backup of the machine before you make critical changes to the machine or active directory. The ability to take just a system state backup is not exposed in the GUI interface of backup. If you wish to take just a system state backup you must use the wbadmin.exe utility. WBadmin.exe is a command line utility. You must first open a command prompt as administrator.
The command to start a system state backup is:
Wbadmin start systemstatebackup –backuptarget:F:
Where F: is the drive where you wish to store the system state backup.
The target volume for a system state backup cannot be a source volume by default. A source volume is any volume that has a file that is included in the backup. To change that behavior, you can add the AllowSSBToAnyVolume registry entry to the server. However, there are known issues with storing a system state backup on a source volume:
Backups can fail. The backup can be modified during the backup process, which might cause the backup to fail.
It causes an inefficient use of target space. Twice the amount of space is necessary for a backup than for the original data. The volume must allocate twice the amount of space for the shadow copy process.
The path for adding the new registry entry is as follows:
HKLM\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\AllowSSBToAnyVolume
Type: DWORD
Value: 1
A value of 0 prevents the storing of system state backup on a source volume. A value of 1 allows the storing of system state backup on a source volume.
The backup process will create a directory on the target drive named WindowsImageBackup. This directory will contain the system state backup of the server. The system state backup of an SBS 2008 server is considerably larger than the same backup on an SBS 2003 server. The average system state backup size is around 11GB.
If you wish to restore a system state backup, you must first reboot the server into Directory Services Restore Mode (DSRM). Once in DSRM, you would open a command prompt with administrator rights and use the following commands to start the restore.
We must first determine the version of the backup that you wish to restore.
The command WBADMIN GET VERSIONS will display all the backups on the machine and the version identifier.
The output will look similar to this:
Backup time: 10/7/2008 3:33 PM
Backup target: Fixed Disk labeled D:
Version identifier: 10/07/2008-20:33
Can Recover: Application(s), System State
This backup job was completed on 10/7/2008 at 3:33pm and was saved to drive D:. The backup job has the ability to restore the system state and is version identifier 10/07/2008-20:33
Once we have located the version identifier, we can initiate the restore by using the following command:
WBADMIN START SYSTEMSTATERECOVERY -version:
Where version id is the version identifier you obtained with the Get Versions command.
For our example the command would be:
WBADMIN START SYSTEMSTATERECOVERY -version: 10/07/2008-20:33
WBADMIN will restore the system state information back to the data from the backup. Once the restore process is complete, you will have to reboot the machine into normal mode to complete the restore.
System State Backups and SBS 2008
[Today's post comes to us courtesy of John Bay]
The normal backup that SBS 2008 creates contains all the necessary information to restore the entire server. The normal SBS backup includes the system state data. You may wish to create a system state backup of the machine before you make critical changes to the machine or active directory. The ability to take just a system state backup is not exposed in the GUI interface of backup. If you wish to take just a system state backup you must use the wbadmin.exe utility. WBadmin.exe is a command line utility. You must first open a command prompt as administrator.
The command to start a system state backup is:
Wbadmin start systemstatebackup –backuptarget:F:
Where F: is the drive where you wish to store the system state backup.
The target volume for a system state backup cannot be a source volume by default. A source volume is any volume that has a file that is included in the backup. To change that behavior, you can add the AllowSSBToAnyVolume registry entry to the server. However, there are known issues with storing a system state backup on a source volume:
Backups can fail. The backup can be modified during the backup process, which might cause the backup to fail.
It causes an inefficient use of target space. Twice the amount of space is necessary for a backup than for the original data. The volume must allocate twice the amount of space for the shadow copy process.
The path for adding the new registry entry is as follows:
HKLM\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\AllowSSBToAnyVolume
Type: DWORD
Value: 1
A value of 0 prevents the storing of system state backup on a source volume. A value of 1 allows the storing of system state backup on a source volume.
The backup process will create a directory on the target drive named WindowsImageBackup. This directory will contain the system state backup of the server. The system state backup of an SBS 2008 server is considerably larger than the same backup on an SBS 2003 server. The average system state backup size is around 11GB.
If you wish to restore a system state backup, you must first reboot the server into Directory Services Restore Mode (DSRM). Once in DSRM, you would open a command prompt with administrator rights and use the following commands to start the restore.
We must first determine the version of the backup that you wish to restore.
The command WBADMIN GET VERSIONS will display all the backups on the machine and the version identifier.
The output will look similar to this:
Backup time: 10/7/2008 3:33 PM
Backup target: Fixed Disk labeled D:
Version identifier: 10/07/2008-20:33
Can Recover: Application(s), System State
This backup job was completed on 10/7/2008 at 3:33pm and was saved to drive D:. The backup job has the ability to restore the system state and is version identifier 10/07/2008-20:33
Once we have located the version identifier, we can initiate the restore by using the following command:
WBADMIN START SYSTEMSTATERECOVERY -version:
Where version id is the version identifier you obtained with the Get Versions command.
For our example the command would be:
WBADMIN START SYSTEMSTATERECOVERY -version: 10/07/2008-20:33
WBADMIN will restore the system state information back to the data from the backup. Once the restore process is complete, you will have to reboot the machine into normal mode to complete the restore.
Monday, March 30, 2009
Download details: Exchange Server 2003 Administration Guide
Download details: Exchange Server 2003 Administration Guide: "Administration Guide for Microsoft Exchange Server 2003
Brief Description
This guide will help you make the most of Microsoft® Exchange Server 2003 by explaining the core concepts of Exchange administration"
Brief Description
This guide will help you make the most of Microsoft® Exchange Server 2003 by explaining the core concepts of Exchange administration"
Subscribe to:
Posts (Atom)
Posts
