Sherman IT

Sherman (Yixiong) Chen

http://dev.mysql.com/doc/refman/5.0/en/faqs-cjk.html#qandaitem-B-11-1-2

Sherman (Yixiong) Chen

<head>
<meta http-equiv="content-type" content="charset=gb2312" />
</head

Sherman (Yixiong) Chen

http://channel9.msdn.com/Blogs/coolstuff/Tip-Auto-Login-Your-Windows-7-User-Account

Sherman (Yixiong) Chen

http://technet.microsoft.com/en-us/library/cc725734%28v=ws.10%29.aspx

Sherman (Yixiong) Chen

Sherman (Yixiong) Chen

http://www.howto-outlook.com/faq/securetemp.htm

Error opening attachments / Cleaning out the Temporary Outlook Files folder

When opening an attachment directly from within Outlook you could get an error message saying that it can’t create the file and to that you need check the permissions on the folder you want to save it in. In most cases the permissions on the folder isn’t the issue but the fact that the folder is “full”. When you open an attachment directly from within Outlook it will first save a copy to a subfolder of the Temporary Internet Files folder. Cleaning out the folder will solve the issue.

Outlook Secure Temp folder

Unfortunately this is easier said than done. The subfolder name Outlook creates (on installation of Outlook) in the Temporary Internet Files folder is quite random. In Outlook 2003 and previous, the name starts with OLK and is followed by up to 4 random numbers or letters. In Outlook 2007 and Outlook 2010, this folder is called Content.Outlook and then has a subfolder which is named with with 8 random numbers and letters. In addition, by default, you cannot simply browse to the folder to clean it out. Getting to the Temporary Outlook Folder can still be accomplished in 2 easy steps though.
Step 1: Locate the folder
The folder location is stored in the registry in the following key;

Outlook 97	`HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Outlook\Security`
Outlook 98	`HKEY_CURRENT_USER\Software\Microsoft\Office\8.5\Outlook\Security`
Outlook 2000	`HKEY_CURRENT_USER\Software\Microsoft\Office\9.0\Outlook\Security`
Outlook 2002/XP	`HKEY_CURRENT_USER\Software\Microsoft\Office\10.0\Outlook\Security`
Outlook 2003	`HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security`
Outlook 2007	`HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security`
Outlook 2010	`HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Security`

Step 2: Get to the folder

Open the OutlookSecureTempFolder registry key from the location provided in Step 1.
Copy the path from the key.
Open Explorer
Paste the address in the Address Bar and press Enter

Use OutlookTools or OutlookTempCleaner

Still not easy enough or just don’t want to go in the Registry to find the folder location? I’ve created two free tools which can do the trick as well.
OutlookTools offers besides locating, opening and cleaning up the SecureTempFolder also quite a lot of additional features to troubleshoot and tweak Outlook.
OutlookTempCleaner focuses only on dealing with the SecureTempFolder and can also be used in (corporate) login and logoff scripts to clean up the folder without any end-user interaction.

OutlookTempCleaner can detect and empty Outlook’s Secure Temp folder automatically for you.

Sherman (Yixiong) Chen

http://www.youtube.com/watch?v=jXAz6vrWMP0&feature=related

Sherman (Yixiong) Chen

Install the software 'Attachment Options'.

Within Outlook, click Tools / Options, you will find a new tab called 'Attachment Security & Options'. Move '.mdb' from the left box to the right one. Click OK.

Done.

Sherman (Yixiong) Chen

1. EasyRecovery
2. FinalData
3. Stellar Phoenix Windows Data Recovery
4. GetDataBack

Sherman (Yixiong) Chen

http://blog.s135.com/linux_ext3_undelete/

Sherman (Yixiong) Chen

http://www.symantec.com/business/support/index?page=content&id=TECH163112

Problem

You must prepare your computers for installation before you install Symantec Endpoint Protection 12.1 client.

Solution

These instructions apply to both the Enterprise and Small Business Editions of Symantec Endpoint Protection 12.1 client. For more specific details at any point, please consult the product help or the implementation guides: Symantec Endpoint Protection Implementation Guide or Symantec Endpoint Protection Small Business Edition Implementation Guide

The following steps should be taken on all computers on which you install the client.

Uninstall currently installed virus protection software

Uninstall any third-party virus protection software. In general, you can use the Windows Add or Remove Programs tool to uninstall programs. However, some programs have special uninstallation routines. See the documentation for the third-party software.

Uninstall any legacy Symantec virus protection software if you do not plan to migrate the settings.

Set administrative rights to your client computers

To install the client software, you need administrative rights to the computer or to the Windows domain. If you do not want to provide users with administrative rights to their computers, use Remote Push Installation to remotely install the client software. Remote Push Installation requires you to have local administrative rights to the computers.

Prepare computers for remote deployment and management

Modify firewall settings to allow communication between Symantec Endpoint Protection Small Business Edition components:
■ Push deployment ports, used on management servers and clients: TCP 139 and 445, UDP 137 and 138, and TCP ephemeral ports.
■ For legacy communications, open UDP port 2967 on all computers.
■ General communication: TCP 8014 (HTTP)/TCP 443 (HTTPS) for management servers. These are the default ports, and may be customized. See Symantec Endpoint Protection 12.1: How to Change the ports used for communication between the Manager and clients.

Prepare Windows XP computers that are installed in workgroups: Windows XP computers that are installed in workgroups do not accept remote deployment. To permit remote deployment, disable Simple File Sharing. Note: This limitation does not apply to computers that are part of a Windows domain. Detailed instructions are provided in the following document: http://www.symantec.com/business/support/index?page=content&id=TECH102867

Prepare Windows Vista, Windows Server 2008, or Windows 7 computers: Windows User Access Control blocks local administrative accounts from remotely accessing remote administrative shares such as C$ and Admin$. Perform the following tasks:
■ Disable the File Sharing Wizard.
■ Enable network discovery by using the Network and Sharing Center.
■ Enable the built-in administrator account and assign a password to the account.
■ Verify that the account has administrator privileges.

Prepare Windows Server 2003 computers for installation using a remote desktop connection: The Symantec Endpoint Protection Manager requires access to the system registry for installation and normal operation. To prepare a computer to install Symantec Endpoint Protection Manager using a remote desktop connection, perform the following tasks:
■ Configure a server that runs Windows Server 2003 to allow remote control.
■ Connect to the server from a remote computer by using a remote console session, or shadow the console session.

Article URL http://www.symantec.com/docs/TECH163112

Sherman (Yixiong) Chen

http://social.technet.microsoft.com/Forums/en-NZ/winservergen/thread/1aecdac4-c274-4d14-85ea-432a9674f70d

How did you create a Distribution point ?
To publish or assign a computer program, you must create a distribution point on the publishing server (I am sure, you must have done that already)
However, FYI... Here are the steps

create a distribution point
Log on to the desired server as an administrator.
Create a shared network folder where you will put the Microsoft Windows Installer package (.msi file) that you want to distribute.
Set permissions on the share to allow access to the distribution package.(Authenticated Users should have READ permissions)
Copy or install the package to the distribution point.
Assign a Package
Computer configuration / Policies / Software Settings / Software installation
Right-click Software installation, point to New, and then click Package.
In the Open dialog box, type the full Universal Naming Convention (UNC) path of the shared installer package that you want. For example, \\FileServer\Share\software.msi

Important: Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
Click Open.
Click Assigned, and then click OK. The package is listed in the right pane of the Group Policy window.
Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in or gpmc.
When the client computer starts, the managed software package is automatically installed.
Along with Software Distribution policy, you can set another policy "Always install with elevated privileges"
User Configuration\Administrative Templates\Windows Components\Windows Installer
This policy directs Windows Installer to use system permissions when it installs any program on the system.

This policy extends elevated privileges to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add/Remove Programs in Control Panel. This policy lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.

If you disable this policy or do not configure it, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.

Caution : Skilled users can take advantage of the permissions this policy grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this policy is not guaranteed to be secure.

Important: This policy appears both in the Computer Configuration and User Configuration folders. To make this policy effective, you must enable the policy in both folders.
Hope that helps.

Sherman (Yixiong) Chen

http://en.allexperts.com/q/Microsoft-Exchange-2094/2008/6/change-email-address.htm

Expert: Tim Fenner - 6/24/2008

Question
How do I change my email address in exchange. I need to change from my oldemail@gmail.com to a newemail@gmail.com. I simply am not able to find this setting in my outlook exchange options

Thanks

AnswerThere are several ways to skin this cat.

1. Change the alias of your account (not recommended unless you are changing the entire name of the account)
2. Add new SMTP address and make it your primary (recommended)
3. Create new account and merge all the Outlook info to the new account (really not recommended)

1. this option has some consequences to note, so read about them here:
http://www.amset.info/exchange/usernamechange.asp

Open Active Directory Users and Computers mmc
Locate your AD account and right click-->Properties
Click on the Mailbox Store tab
Change the alias
Wait for Recipient Update Services to refresh your email address, check the Email Addresses tab in 15 minutes

2.
Right click on user again, and choose Properties.
Click on the "Email Addresses" tab.
Add the new email address in the same format as your existing email addresses. Leave the old address in place.
Change the default (set as primary) address to the new one.
By doing this, any email sent in on the old address will still be delivered, but all new email will go out with the new address.
uncheck auto update email addresses based on recipient policy, or your primary will be switched back to the alias generated address

3.
LOTS of work, but you can do it, if you really want to.

Sherman (Yixiong) Chen

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

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center

This article was previously published under Q324750

For a Microsoft Windows 2000 version of this article, see 302430

(http://support.microsoft.com/kb/302430/EN-US/ )

.

Expand all | Collapse all

SUMMARY

You (as an administrator) can use Group Policy to assign or to publish software to users or computers in a domain. Additionally, it is useful to be able to deploy software based on group membership. A Group Policy object (GPO) is usually applied only to members of an organizational unit (OU) to which the GPO is linked. Because a user cannot be located in several OUs at the same time, you must be able to apply Group Policy settings outside the boundaries of OUs. This article describes how to have your software deployment policy applied to users who are not in an OU.

Assign a program to a group

Create a folder to hold the Windows Installer package on a server. Share the folder by applying permissions that let users and computers read and run these files. Then, copy the MSI package files into this location.
From a Windows Server 2003-based computer in the domain, log on as a domain administrator, and then start Active Directory Users and Computers.
In Active Directory Users and Computers, right-click the container to which you want to link the GPOs, and then click Properties.
Click the Group Policy tab, and then click New to create a new GPO for installing the Windows Installer package. Give the new GPO a descriptive name.
Click the new GPO, and then click Edit.

The Group Policy Object Editor starts.
Right-click the Software Settings folder under either Computer Configuration or User Configuration, point to New, and then click Package.

Notes
- The Software Settings folder under Computer Configuration contains software settings that apply to all users who log on to the computer. This folder contains software installation settings. It may also contain other settings that are put there by independent software vendors.
- The Software Settings folder under User Configuration contains software settings that apply to users regardless of which computer they log on to. This folder also contains software installation settings. It may contain other settings that are put there by independent software vendors.
In the Open dialog box, type the Universal Naming Convention (UNC) path of the Windows Installer file (.msi) for this package in the File name box, and then click Open.

Note If the Windows Installer file resides on the local hard disk, do not use a local path. Instead, use the UNC path of the local computer to indicate the location of the installation files. A UNC path takes the form \\servername\sharename\path\filename.msi.
In the Deploy Software dialog box, do one of the following:
- Click Assigned to specify that the application is deployed as assigned and that default settings are used for deployment properties.
- Click Advanced to specify that you are manually editing the package properties instead of accepting the defaults. You can also choose between assign and publish for the deployment method.
When you are prompted to choose between Advanced and Assigned, click Assigned unless you have to modify the advanced options.
Click OK.

The software package appears in the details pane of the Group Policy Object Editor.
Close the Group Policy Object Editor.
In the GPO Properties dialog box, click the GPO, and then click Properties.
Click the Security tab.
Click Authenticated Users in the Group or user names list, and then click Remove.
Click Add, select the security group that you want this policy applied to, and then click OK to add the security group to the list.
Select the security group, and then under Permissions for Users, click to select the READ and the Apply Group Policy check boxes in the Allow column.
Click Apply, click OK, click Apply, and then click OK.

Changes to a GPO are not immediately applied on the target computers. Instead, changes are applied according to the current Group Policy update interval. You can use the Secedit.exe command-line tool to impose GPO settings upon a target workstation immediately. For more information about how to use Secedit.exe, see the Windows Server 2003 Help and Support Center.

Sherman (Yixiong) Chen

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

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center

This article was previously published under Q302430

For a Microsoft Windows Server 2003 version of this article, see

324750

(http://support.microsoft.com/kb/324750/ )

How to assign software to a specific group by using Group Policy in Windows Server 2003

Notice

This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center

(http://support.microsoft.com/?scid=http%3a%2f%2fsupport.microsoft.com%2fwin2000)

is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy

(http://support.microsoft.com/lifecycle/)

.

Expand all | Collapse all

SUMMARY

You can use Group Policy to assign or to publish software to users or computers in a domain. Additionally, it is useful to be able to deploy software based on group membership. A Group Policy object (GPO) is usually applied only to members of an organizational unit (OU) to which the GPO is linked. Because a user cannot be located in several OUs at the same time, you must be able to apply Group Policy settings outside the boundaries of OUs. This article describes how to have your software deployment policy applied to users who are not in an OU.

Assign a program to a group

Create a folder to hold the MSI package on a server. Share the folder by applying permissions that let users and computers read and run these files. Then, copy the MSI package files into this location.
From a Windows 2000-based computer in the domain, log on as a domain administrator, and then start Active Directory Users and Computers.

Note You can apply Group Policy settings to domains, sites, and OUs.
In Active Directory Users and Computers, right-click the container to which you want to link the GPO, click Properties, and then click the Group Policy tab.
Create a new GPO for installing your MSI package, and then give the new GPO a descriptive name.
While the new GPO is selected, click Edit. This starts the Group Policy Object Editor.
Open and then right-click Software installation in the GPO, and then click New Package.
You are prompted for the path of the Windows Installer file (.msi) for this package. View the network location that contains the Windows Installer file, click the file, and then click Open.

Warning If the Windows Installer file resides on the local hard disk, do not use a local path. Instead, use the UNC path of the local computer to indicate the location of the installation files. A UNC path takes the form \\servername\sharename\path\filename.msi.
When you are prompted to choose between Assigned and Advanced Published or Assigned, click Assigned unless you have to modify the advanced options. You should now see the software package in the details pane of the Group Policy Object Editor.
In Active Directory Users and Computers, click the container to which you linked your GPO. Right-click that container, click Properties, and then click the Group Policy tab.
Click your GPO, and then click Properties.
Click the Security tab, and then remove Authenticated Users from the list.
Click Add, and then select the security group which you plan to have this policy applied to add it to the list.
Select your security group, and then give them Read and "Apply Group Policy" permissions.

Changes to a GPO are not immediately applied on the target computers. Instead, changes are applied according to the current Group Policy update interval. You can use the Secedit.exe command-line tool to impose GPO settings upon a target workstation immediately. For more information about how to use Secedit.exe to force a Group Policy update, click the following article number to view the article in the Microsoft Knowledge Base:

227302

(http://support.microsoft.com/kb/227302/ )

Using SECEDIT to force a Group Policy refresh immediately

Sherman (Yixiong) Chen

http://defaultpasswords.in/

Sherman (Yixiong) Chen

http://technet.microsoft.com/en-us/library/cc757597(v=ws.10)

Changing the Group Policy Refresh Interval

1 out of 2 rated this helpful - Rate this topic

Updated: March 28, 2003
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

Administrators can change the default refresh policy interval setting by using one of these policy settings: Group Policy Refresh Interval for Computers,Group Policy Refresh Interval for Domain Controllers, or Group Policy refresh Interval for Users. By using these settings, you can stipulate an update rate from zero to 64,800 minutes (45 days). You can also set the policy to Turn off background refresh of Group Policy.
Important

When you set the refresh interval to 0 minutes, the computer tries to update Group Policy every seven seconds. Because such updates might interfere with users’ work and increase network traffic, very short update intervals are appropriate only in test environments.

Group Policy Refresh Interval for Computers

This setting specifies how often Group Policy for computers is updated in the background. It specifies a background update rate only for Group Policy settings under Computer Configuration. Computer Group Policy is updated in the background every 90 minutes by default, with a random offset of 0 to 30 minutes. In addition to background updates, computer Group Policy is always updated when the system starts. This policy setting is available in the Group Policy Object Editor under Computer Configuration\Administrative Templates\System\Group Policy.

Group Policy Refresh Interval for Domain Controllers

This setting specifies how often Group Policy is updated in the background on domain controllers. By default, Group Policy on domain controllers is updated every five minutes. This policy setting is available in the Group Policy Object Editor under Computer Configuration\Administrative Templates\System\Group Policy.

Group Policy Refresh Interval for Users

This setting specifies how frequently Group Policy is updated in the background only for the Group Policy settings in the User Configuration folder. In addition to background updates, Group Policy for users is always updated when users log on. This policy is in the User Configuration\Administrative Templates\System\Group Policy item.

Turn off background refresh of Group Policy

This policy prevents Group Policy settings from being updated while the computer is in use. It applies to Group Policy for computers, users, and domain controllers. This policy setting is available in Computer Configuration\Administrative Templates\System\Group Policy item.

Running Command Line Options to Refresh Policy

From a given computer, you can refresh the settings that are deployed to that computer by using the Gpupdate.exe tool. One reason this is useful is to ensure that security settings are enforced. Table 2.7 describes parameters for Gpupdate.exe. The Gpupdate.exe tool is used in Windows Server 2003 and Windows XP environments and replaces the /refreshpolicy option previously used with the secedit command. For Windows 2000, continue to use the secedit /refreshpolicy command.
The Gpudate.exe tool uses the following syntax:

Copy

          gpupdate [/target:{computer|user}] [/force] [/wait:value] [/logoff] [/boot]

Table 2.7 Gpudate.exe Parameters

Parameter	Description
/target:{computer\|user}	Depending on what target you specify, Gpupdate.exe processes the computer settings, the current user settings, or both. By default, both the computer and the user settings are processed.
/force	Reapplies all settings and ignores processing optimizations.
/wait: value	Specifies the number of seconds that policy processing waits to finish. The default is 600 seconds. A value of 0 means no wait; -1 means wait indefinitely.
/logoff	Logs off after the policy refresh completes. This is required for Group Policy client-side extensions that do not process on a background refresh cycle but do process when the user logs on, such as user Software Installation and Folder Redirection. This option has no effect if there are no extensions called that require the user to log off.
/boot	Restarts the computer after the policy refresh completes. This is required for those Group Policy client-side extensions that do not process on a background refresh cycle but do process when the computer starts up, such as computer Software Installation, for example. This option has no effect if there are no extensions called that require the computer to be restarted.
/?	Displays Help at the command prompt.

Sherman (Yixiong) Chen

http://www.petri.co.il/forums/showthread.php?t=50852

Re: Exchange 2010 Certificates on Outlook Anywhere

Exchange 2010 has all the tools you need to generate your own self signed cert without buggering about with CAs or anything like that.

Use the Exchange Shell:

Quote:

[PS] C:\Windows\system32>help New-ExchangeCertificate

NAME
New-ExchangeCertificate

SYNOPSIS
Use the New-ExchangeCertificate cmdlet to create a self-signed certificate, renew an existing self-signed certifica
te, or generate a new certificate request for obtaining a certificate from a certification authority (CA).
There are many variables that you must consider when configuring certificates for Secure Sockets Layer (SSL) and Tr
ansport Layer Security (TLS). You must understand how these variables may affect your overall configuration. For mo
re information and before you continue, see Understanding TLS Certificates.

Quote:

[PS] C:\Windows\system32>help Enable-ExchangeCertificate

NAME
Enable-ExchangeCertificate

SYNOPSIS
Use the Enable-ExchangeCertificate cmdlet to enable an existing certificate in the local certificate store for Exch
ange services such as Internet Information Services (IIS), SMTP, POP, IMAP, and Unified Messaging (UM).
There are many factors to consider when you configure certificates for Transport Layer Security (TLS) and Secure So
ckets Layer (SSL) services. You must understand how these factors may affect your overall configuration. Before you
continue, read Understanding TLS Certificates.
Don't use the Enable-ExchangeCertificate cmdlet to enable a wildcard certificate for POP and IMAP services. To enab
le a wildcard certificate, you must use the Set-ImapSettings or Set-PopSettings cmdlets with the fully qualified do
main name (FQDN) of the service.
Don't use the Enable-ExchangeCertificate cmdlet to enable a certificate for federation. Certificates used for feder
ation trusts are managed by using the New-FederationTrust and Set-FederationTrust cmdlets.

Sherman (Yixiong) Chen

Telnet to the firewall.
Log in.

Run the 'login' command.
>login
Password:

Run the following command -

#sh conn

Copy all the output to Notepad.
Open the txt file in Excel delimited by space.

Order them by 'Bytes'.

Sherman (Yixiong) Chen

File / Options / Trust Centre / Trust Centre Settings / Protected View.

Sherman (Yixiong) Chen

One of the Bell DNS servers have problems.

On our DNS server, choose e.g. NTS3850SERVER / Forwarders, right-click on Forwarders, then choose Properties. On the Forwarders tab, add another Bell DNS server IP address (a working one), and 'Up' it to the top, then we can open any website now.

Sherman (Yixiong) Chen

Solution:
Open Symantec Endpoint Protection.
Network Threat Protection / Options / Change Settings.
Select 'Allow IP traffic'.

Sherman (Yixiong) Chen

http://www.doodle.com/

Sherman (Yixiong) Chen

Format Factory 格式工厂

Sherman (Yixiong) Chen

Look4computer Tech Inc

1-2800 14th Ave, Markham, ON L3R 0E4
905-479-8922

Sherman (Yixiong) Chen

Dual page copy.
1-sided to 2 sided.

Sherman (Yixiong) Chen

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/7a12dd3a-ab9e-41a5-af42-6087be993559/

Hi,
We can configure transport rule to restrict send messages.
Apply rule to messages
from a member of team1@xxx.com
Delete the message without notifying anyone
except when the message is sent to member of team2@xxx.com /except when any of the recipients in the To field is a member ofteam2@xxx.com.
We can use Message Delivery Restriction settings to restrict to receive messages.
1. Right click on team1@xxx.com and properties.
2. Navigate to "Message Delivery Restriction".
3. Select only senders in the following list.
4. Add team2@xxx.com to the list.
Regards,
Xiu

Sherman (Yixiong) Chen

http://ffyu2007.blog.163.com/blog/static/3359057020079261255271/

易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』

2007-10-26 01:02:55| 分类：小菜学电脑 | 标签： |字号大中小订阅

2010年的更新：
此文乃本人原创，07年到现在，中间也有过一些小的改动，力求写得更完美。如果别的网站上有与本文极为相似的文章，那纯属本文的“盗版”。很多人弄好了ISO但却装不上系统，就是找不到GHO文件，究其原因只有以下两种：
1.disk1文件夹下缺少ghost程序。这是一个以“ghost”命名的以exe为后缀名的可执行文件。
2.用于引导GHO的IMG文件无法引导GHO，解决这个问题最简单的方法就是，从哪个系统提取出来的GHO，就用这个系统的IMG文件，而且连名字也不要改。要改的话也只能改IMG文件名。IMG文件内部是可以编辑的，其内部已经设定好了默认的GHO名字，GHO若改成其他名字，自然就无法引导。可以试着自己修改一下IMG文件：http://hi.baidu.com/masoso/blog/item/caaff5d524d778c250da4b78.html 易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』 - 烂漫飞鱼 - 烂漫飞鱼

易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』 - 烂漫飞鱼 - 烂漫飞鱼

以下是我制作的方法过程，给新手们做个参考，
尽量说简单点，通俗一点，希望大家都能看懂。

先说明一下，易启动可以制作多种启动盘，可以是单个系统的启动盘，也可以是N合1个系统的启动盘;可以用原版系统(带有i386文件夹)制作，也可以用ghost系统制作。本文所讲述的是用ghost系统制作单个系统的启动盘的方法。

一. 准备需要的工具和相关文件
1.易启动
下载地址：EasyBoot V5.12
2.虚拟机
vmware或virtual pc (新手推荐用用virtual pc，原因是这个比较简单易懂)虚拟机是用来做ISO测试的，测试没问题就可以放心刻盘了。如果你实在不懂虚拟机，那么制作启动盘的过程中，一对要细心，不能出错，确认无误后方可刻盘，要不然就得浪费一张盘了。 virtual pc下载地址：霏凡软件站汉化补丁：华军软件园
3.img文件
要用的一些常用工具的img文件，比如DOS、PQ分区等。可以到这里下载http://chenlin.atedu.net/ 或http://down.x6x8.com/soft/101/101_1.html 如果你下载有别的ghost系统ISO，可以将其解压，在文件夹EZBOOT里面也有img 文件。
4.ghost镜像文件
这就是封装的ghost系统的ghost镜像文件，下载个自己喜欢的系统，提取出里面的ghost镜像。img文件和ghost镜像文件的提取，可以把直接ISO解压复制提取，也可以用软件winimage提取(推荐) winimage下载地址：绿色软件站
二.制作启动盘背景图
要用到的工具：photoshop和ACDSee V5.0 龙漫实用典藏版(ACDSee下载页面：绿色软件站)
易启动仅支持640X480 256色的BMP格式的图片，但为了画面更好看一些，可以用800X600 64K色(16位)BMP格式的.用photoshop设置好图片大小为800X600，图形－模式－索引颜色，8位/通道，保存为BMP格式。由于易启动无法识别以以上方法用photoshop制作的BMP格式的图片，因此要用ACDSee将图片转为BMP格式，保存名为BACK。
三.安装易启动
默认安装在C:\Program Files下,可自己更改。安装过程一路点击下一步即可。
四.添加ghost镜像文件、img文件和背景图像。
打开安装根目录EasyBoot，里面有名为disk1和resource两个文件夹和一些文件，
而我们自己要用的文件文件（img文件和ghost镜像文件）是存放disk1和它的次级文件夹ezboot内,如下所示：
EasyBoot
|____disk1 ghost镜像文件放这里
|
|___ezboot img文件、制作好的背景图片放这里，覆盖原有的即可。
重要说明：disk1文件夹中应该有MOUSE和GHOST这两个程序。MOUSE是鼠标程序（有了这个，进入ghost11的时候，可用鼠标操作）如图1，GHOST则是运行ghost 11和在ghost环境下恢复系统镜像时所必需的。其他文件是本人自行添加的，非必要。
图1：
易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』 - 烂漫飞鱼 - 烂漫飞鱼

五.设置易启动
刚安装好的易启动，打开后如图2所示。
图2：
易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』 - 烂漫飞鱼 - 烂漫飞鱼

设置下面一些选项，没有提到的默认即可。
1.文件
等待时间：
进入启动盘后，如果不进行任何操作，将会在等待时间过后，从硬盘启动计算机。易启动安装后默认的等待时间为30秒，一般可设为10秒。
显示logo：
进入启动盘界面之前，会先显示logo(也就是一张图片罢了)，这个没必要，可不选。
背景图像：
就是自己制作的背景图片，默认名为BACK。
将自己弄好的图片复制到易启动的安装目录ezboot文件夹下，覆盖原有的的图片，然后回到易启动设置界面，点击选项－配置－“屏幕模式” 选择64k色(16位)，“屏幕分辨率”选择800x600,点击确定。如图3。回到易启动设置界面，点击“保存”。然后关闭易启动，重新运行后，即可看到背景图像已换成自己的了。
图3：

快捷键操作方式：
一般选择“直接执行命令”，即按下快捷键后，立即运行该键所对应的菜单条命令。
2.屏幕布局
相信你也不喜欢默认的布局，那就全删了吧，删除方法如下图4所示：
图4：

3.文本显示
文本显示1：
使用数字(1－4)或光标键(↑和↓)... ..这个谁都懂，多余了，也删了吧。文本显示2：
=== Windows XP/98 2合1光盘 === .....这里就改成自己要制作的光盘的名称，在“文本内容”把文字改过来就好，如图5。当然也可以删了。
图5：

4.菜单条
易启动支持如下几种菜单命令：
(1) 执行映像 run xx.bin / xx.img / xx.ima
(2) 执行菜单 run xx.ezb (用于主、子菜单间的互相调用）
(3) 特殊功能 boot 80 (从硬盘启动) Reboot (重新启动计算机)。这两个命令在易启动安装后，默认存在。
接下来先了解一下img文件所对应的中文名，如图6：
图6：
易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』 - 烂漫飞鱼 - 烂漫飞鱼

img文件所对应的菜单条命令,如下所示：

ing文件名	对应的菜单条命令
GHOSTXP.IMG	run ghostxp.img(注：从哪提取出来的ghost镜像，就用哪的img文件吧，而且名字也不要改，否则将无法引导)
DOS 工具集合	run dostools.ima
PQ 8.05 繁体版	run pm805T.img
DM 9.57 万用版	run dm957.ima
手动运行 Ghost11	run ghost11.img
硬盘检测修复程序	run xly2007.img
微软内存检测工具	run windiag.img
一键清除CMOS密码	run CMOS.img
windows用户密码破解	run password.img
从硬盘启动计算机	boot 80

注：易启动安装后已内置硬盘启动命令(boot 80)、重启电脑的命令(Reboot)。
run和img文件名之间要有一个空格。无需区分大小写。
菜单条设置详细说明：(有些设置貌似很难理解，新手只有多动手才能更了解设置方法)

高亮属性	鼠标指到的项，改项就改变颜色，改变的颜色为前景色所设置的颜色。此种颜色在“光盘启动界面预览”中可看到。
使用图像文本	勾选此项后，直接使用图像中的文本，把虚线框放置对应的图像中的文字即可。
正常属性	背景色就不用说了，前景色就是字体的实际颜色，在“光盘启动界面预览”不可见，只有刻成盘后，启动该盘时才可见。简单的说，启动系统盘时，首先看到的字体颜色是，“正常属性”的前景色，当鼠标指向某项后，该项所显示的颜色是“高亮属性”的前景色。相信装过系统的人都懂。
快捷键	就是不用鼠标，在键盘上按下该键，则系统盘就会执行该键所对应的命令。
设置为缺省	易启动默认的缺省设置。此项主要应用于“从硬盘启动”。将“从硬盘启动”的快捷设置为缺省，则光盘启动后，如果未进行任何操作，在等待时间过后，将默认从硬盘启动计算机。
添加/插入/删除/上移/下移	点击添加或插入都可添加一项新的菜单条;删除/上移/下移就不用多做说明了。

接下来是托动菜单条到合适的位置，方法如下：
在光盘启动界面预览窗口中，双击任一菜单条，移动虚线框到合适位置，再单击鼠标右键即可完成移动。连续三次单击菜单条，可调整虚线框大小。为了让菜单条更对齐一些，可以将任两项的间隔距离设置成相等的一个数值；将每一项首字到最左端的距离也设置成一样的数值。
间隔距离相等：
比如为40。点击第一项菜单条，可以看到“左上角坐标”行和列的数值，“右下角坐标”行和列的数值。假设“左上角坐标”行为120，那么第二项菜单条的“左上角坐标”应该为120+40=160.依次类推..
首字到最左端的距离相同:
以第一项菜单条为准，若该项“左上角坐标”列为120，则其他菜单条的“左上角坐标”列也应该为120。
5.其他
功能键：
易启动安装后，默认的“其他”选项卡中有功能键quit(不知道是什么)和reboot(重启)如图7
图7：

reboot的快捷键为r,即按r键重新启动电脑。这两个都保留默认的即可。
显示进度条：
即等待时间的进度条。“左上角坐标”行的数值—“右下角坐标”行的数值＝进度条的大小
“左上角坐标”列的数值为进度条左端到到背景图最左端的距离；“右下角坐标”列的数值则为进度条右端到背景最左端的距离。如果要进度条的长度占满全屏，则这两项可设为1和799
显示倒计时：这项就不用多说了吧。
六.保存所有设置
返回到“文件”选项卡，双击右侧的“保存”即可保存之前的全部设置。到这里全部设置就完成了，有些设置没有提到，默认即可。比如点击“等待时间”后面的字母p，可设置光盘密码。一般都不用设置密码。
七.制作ISO
在“文件”选项卡中单击“制作ISO”，在弹出的窗口中，光盘文件目录、引导文件，这两项无需改动，默认即可。在“选项”栏选中“优化光盘文件”项，如果需要支持小写文件名，还要选择“使用Joliet”，“CD卷标”可以自行设置，ISO文件名：默认的路径不可用，请单击右边的“浏览”按钮更改路径，并填写好文件名。
最后一步单击“制作”按钮即可生成一个启动安装光盘的ISO文件。然后用虚拟机测试一下ISO文件，确认没有问题后，就可以用刻录软件进行刻盘了。

Sherman (Yixiong) Chen

Can not logon. Error message: The Group Policy Client service failed the logon. Access is denied.

Refer to -
http://support.microsoft.com/kb/947215

Find an un-used user account. Change it into the user name you have problem logging on.

Sherman (Yixiong) Chen

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

Sherman (Yixiong) Chen

http://web1.toshiba.ca/support/isg/drivers/Common/wireless/howto/index.htm

Sherman (Yixiong) Chen

splashtop sos

anydesk

aeroadmin

Zoom Meeting

Teamviewer

Remote Utilities

http://www.ammyy.com

Sherman (Yixiong) Chen

http://www.advancedinstaller.com/

Sherman (Yixiong) Chen

http://forum.canadameet.me/showthread.php?t=247068

现在的应用开发，基本上已经完全被web统治了,也就是客户端完全browser based.

技术上, Web开发的前端Javascript , CSS越来越重要。 Javascript 远远超出了任何人对它的期许，而且势不可当，开源Javascript framework ( Prototype, JQuery, YUI,Extjs 等)，取得了无比辉煌和耀眼的成功。而CSS在网页风格设计和布局开发里成为王者，任何serious的web开发都会使用CSS stylesheet.

与此同时，客户服务端混合编程模型一直是主流的开发平台。Java 和PHP, Ruby等程序语言世界 , MVC frameworks(Model-view-controller frameworks) 盛行，Struts / JFaces , Sprint MVC , Ruby on Rails , Django, Symfony 等等。

.NET方面, 一直以来，以Web form模型为主，占据企业级市场不少份额。最近也发布了ASP.NET MVC Framework 加入MVC frameworks潮流。

另外，实践中,基于大型服务软件平台进行定制开发,一直是企业级应用的主要选择之一。整体上说, IBM的Lotus notes 和 Microsoft 的SharePoint正在拉锯这个市场。

在Java 服务端世界，IBM Websphere占据了主要份额开源的Tomcat, JBOSS等也非常流行

Sherman (Yixiong) Chen

http://www.symantec.com/business/support/index?page=content&id=TECH18273

Sherman (Yixiong) Chen

ISO Workshop

http://www.imgburn.com/index.php?act=download

Sherman (Yixiong) Chen

http://www.dvddecrypter.org.uk/

Sherman (Yixiong) Chen

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

System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center

This article was previously published under Q324750

For a Microsoft Windows 2000 version of this article, see 302430 .

SUMMARY

You (as an administrator) can use Group Policy to assign or to publish software to users or computers in a domain. Additionally, it is useful to be able to deploy software based on group membership. A Group Policy object (GPO) is usually applied only to members of an organizational unit (OU) to which the GPO is linked. Because a user cannot be located in several OUs at the same time, you must be able to apply Group Policy settings outside the boundaries of OUs. This article describes how to have your software deployment policy applied to users who are not in an OU.

Back to the top

Assign a program to a group

Create a folder to hold the Windows Installer package on a server. Share the folder by applying permissions that let users and computers read and run these files. Then, copy the MSI package files into this location.
From a Windows Server 2003-based computer in the domain, log on as a domain administrator, and then start Active Directory Users and Computers.
In Active Directory Users and Computers, right-click the container to which you want to link the GPOs, and then click Properties.
Click the Group Policy tab, and then click New to create a new GPO for installing the Windows Installer package. Give the new GPO a descriptive name.
Click the new GPO, and then click Edit.

The Group Policy Object Editor starts.
Right-click the Software Settings folder under either Computer Configuration or User Configuration, point to New, and then click Package.

Notes
- The Software Settings folder under Computer Configuration contains software settings that apply to all users who log on to the computer. This folder contains software installation settings. It may also contain other settings that are put there by independent software vendors.
- The Software Settings folder under User Configuration contains software settings that apply to users regardless of which computer they log on to. This folder also contains software installation settings. It may contain other settings that are put there by independent software vendors.
In the Open dialog box, type the Universal Naming Convention (UNC) path of the Windows Installer file (.msi) for this package in the File name box, and then click Open.

Note If the Windows Installer file resides on the local hard disk, do not use a local path. Instead, use the UNC path of the local computer to indicate the location of the installation files. A UNC path takes the form \\servername\sharename\path\filename.msi.
In the Deploy Software dialog box, do one of the following:
- Click Assigned to specify that the application is deployed as assigned and that default settings are used for deployment properties.
- Click Advanced to specify that you are manually editing the package properties instead of accepting the defaults. You can also choose between assign and publish for the deployment method.
When you are prompted to choose between Advanced and Assigned, click Assigned unless you have to modify the advanced options.
Click OK.

The software package appears in the details pane of the Group Policy Object Editor.
Close the Group Policy Object Editor.
In the GPO Properties dialog box, click the GPO, and then click Properties.
Click the Security tab.
Click Authenticated Users in the Group or user names list, and then click Remove.
Click Add, select the security group that you want this policy applied to, and then click OK to add the security group to the list.
Select the security group, and then under Permissions for Users, click to select the READ and theApply Group Policy check boxes in the Allow column.
Click Apply, click OK, click Apply, and then click OK.

Changes to a GPO are not immediately applied on the target computers. Instead, changes are applied according to the current Group Policy update interval. You can use the Secedit.exe command-line tool to impose GPO settings upon a target workstation immediately. For more information about how to use Secedit.exe, see the Windows Server 2003 Help and Support Center.

227302 Using SECEDIT to force a Group Policy refresh immediately

Sherman (Yixiong) Chen

http://www.windowsitpro.com/article/tips/jsi-tip-4989-how-do-i-use-group-policy-to-apply-security-patches-in-windows-2000-#4

JSI Tip 4989. How do I use Group Policy to apply security patches in Windows 2000?

Jerold Schulman

Windows IT Pro

InstantDoc ID #76295

Rating: (0)

inShare

NOTE: The text in the following Microsoft Knowledge Base article is provided so that the site search can find this page. Please click the Knowledge Base link to insure that you are reading the most current information.
Microsoft Knowledge Base article Q314273 contains:

IN THIS TASK

SUMMARY

How to Create a Security Patch .msi Package

How to Create a Security Patch Distribution Point

How to Create a Security Patch GPO

REFERENCES

SUMMARY

This step-by-step article describes how to use Group Policy to apply security patches. You must be a member of the Administrators group on a computer that is running either Windows 2000 Server or Windows 2000 Advanced Server to perform all of the procedures that are described in this article.

NOTE : Download the security patches that are referred to in this article before you start the procedures that are described in this article.

back to the top

HOW TO CREATE A SECURITY PATCH .MSI PACKAGE
NOTE : You use Windows Installer to convert the .exe patch file to an .msi file. Windows Installer is located at the following path on the Windows 2000 installation media.
Valueadd\3rd Party\Mgm\Winstle\Swiadmle.msi

Click Start , point to Programs , point to Veritas Software, and then click Veritas Discover .

Click Next .

Type either the name of the patch or a general label (for example, type security patches ) in the Specify the name of the application for which you are building the installation box.

Type the path to the new package and the name for the new package (for example, typec:\adminpackages\securitypatch.msi ) in the Specify the Path and file name for the data file where the information on this installation will be kept box, and then click Next .

Click the drive on which you want to store the temporary work files for Windows Installer, and then click Next .

Under Available Drives , click the drive on which you want to install the .msi package, click Add , and then click Next .

Accept the defaults, and then click Next .

Wait for the program to take a snapshot of your computer (this action may take several minutes depending on the size of your computer), and then click OK when this action is completed.

In the Look in box, click the location of the .exe file that you want to convert, and then click Open .

After the .exe file completes the installation, click Reboot Later , and then run Windows Installer again.

NOTE : Do not restart the computer after the .exe file completes the installation.

Click Start , point to Programs , point to Veritas Software, and then click Veritas Discover .

Click Perform the After snapshot now , and then clickNext .

Windows Installer takes the After snapshot, and then creates the new .msi file in the specified location.

NOTE : You receive an error message if problems occur during the conversion process. If you receive an error message, you may have to repeat this procedure to convert the .nai file to an .msi file.
back to the top
HOW TO CREATE A SECURITY PATCH DISTRIBUTION POINT

Click Start , point to Programs , point to Administrative Tools , and then click Computer Management .

Right-click Computer Management (Local) , and then clickConnect to another computer .

Click the computer on which the patch package is located in the Name box, and then click OK .

In the console tree, click to expand System Tools , click to expand Shared Folders , right-click Shares , and then clickNew File Share .

Type the path to the patch package distribution point in theFolder to share box.

Type the name for the distribution point in the Share namebox.

Type a description for the distribution point in the Share description box.

Click Next , and then click Yes to create the shared folder.

Click Finish .

Click No when you receive the message that asks if you want to create another shared folder.

back to the top
HOW TO CREATE A SECURITY PATCH GPO
To create a security patch Group Policy object (GPO):

Click Start , point to Programs , point to Administrative Tools , and then click Active Directory Users and Computers .

Right-click your domain name, and then click Properties .

Click the Group Policy tab, and then click New .

Type the name of the new GPO (for example, type Security Patches ) in the Group Policy Objects Links box (replace the existing name).

Click the newly created GPO, and then click Edit .

In the console tree, under the User Configuration node, click to expand Software Settings .

Right-click Software Installation , point to New , and then click Package .

In the Look in box, type the Universal Naming Convention (UNC) name for the security patch package Setup program that you created in the "How to Create a Security Patch .msi Package" section, and then click Open .

NOTE : If Windows does not use the UNC name to locate the security patch .msi package, you receive the following message:

Cannot verify path is a network location message. If this package is not available on a network share, client are not able to install it. Are you sure you want to deploy this package.

Click Assigned in the Deployment Method box, and then click OK .

In the Group Policy dialog box, click Software Installation , right-click the GPO that you created in step 4 in the details pane, and then click Properties .

Click the Deployment tab, and then click Auto-install this application by file extension activation in the Deployment Options box.

back to the top
REFERENCES
For additional information about the procedures that are described in this article, click the article numbers below to view the articles in the Microsoft Knowledge Base:
Q224330 Assigning a Windows Installer Package with Minimal Interaction

Q302430 How to Deploy Software to a Specific Group By Using a Group Policy
back to the top

30 December 2012

26 November 2012

26 October 2012

25 October 2012

11 September 2012

Error opening attachments / Cleaning out the Temporary Outlook Files folder

Outlook Secure Temp folder

Use OutlookTools or OutlookTempCleaner

06 September 2012

04 September 2012

29 August 2012

28 August 2012

23 August 2012

Problem

Solution

21 August 2012

Assign a program to a group

Notice

Assign a program to a group

13 August 2012

08 August 2012

Changing the Group Policy Refresh Interval

Group Policy Refresh Interval for Computers

Group Policy Refresh Interval for Domain Controllers

Group Policy Refresh Interval for Users

Turn off background refresh of Group Policy

Running Command Line Options to Refresh Policy

02 August 2012

31 July 2012

25 July 2012

05 July 2012

04 July 2012

03 July 2012

07 June 2012

Look4computer Tech Inc

06 June 2012

30 May 2012

07 May 2012

易启动(EasyBoot)制作Ghost系统启动盘简易教程『图解』

10 April 2012

05 April 2012

29 February 2012

23 January 2012

19 January 2012

Assign a program to a group

JSI Tip 4989. How do I use Group Policy to apply security patches in Windows 2000?

IN THIS TASK

SUMMARY

HOW TO CREATE A SECURITY PATCH .MSI PACKAGE

HOW TO CREATE A SECURITY PATCH DISTRIBUTION POINT

HOW TO CREATE A SECURITY PATCH GPO

REFERENCES

Related Content: