-Two slides of tender beef steak (3-5 cm thick)
-Rub the steak with vegetable oil, wait for few minutes then season with salt and pepper otherwise the salt will start to eat into the meat and dry it out.
-Heat the solid pan in 200 degree in 15 minutes before start cooking
-Put the steak into the pan and don't touch it until 2 minutes then turn over. Put more oil if it is not sizzling but keep the heat high.
-Sear for 2 minutes more and then turn again.
-Take the steak out and leave it to rest for 5 minutes before you serve.
Remember the steak will continue to cook while it is resting.
...I am starve :-)
3 Jun 2012
Move BESX to new server
1. Install BESX on new server
2. Modify firewall if any
3. Download and install BlackBerry Enterprise Transporter files
Make sure BlackBerry Administration Service type on both old and new BESX must be the same (Active Directory or BlackBerry Administration Service authentication) otherwise you will get the BAS assignment error when migrating.
Good luck
2. Modify firewall if any
3. Download and install BlackBerry Enterprise Transporter files
- Browse to http://us.blackberry.com/support/server_resourcekit.jsp
- Click on Download BlackBerry Enterprise Resource Kit
- Select BlackBerry Enterprise Resource Kit V5.0 SP3. Don't click on Next button but just look down and download BlackBerry Enterprise Transporter 5.0 Service Pack 3
Make sure BlackBerry Administration Service type on both old and new BESX must be the same (Active Directory or BlackBerry Administration Service authentication) otherwise you will get the BAS assignment error when migrating.
Good luck
30 May 2012
Place a sent message in Sent Items of Shared Mailbox (Outlook/Exchange 2010)
When user send email from a shared mailbox the message is placed in the Sent Items of the user's mailbox.
To place the sent message in the Sent Items of the Shared mailbox you have to do 2 simple things
1. Apply the Hotfix KH2459115 (http://support.microsoft.com/kb/2459115) or it can already be installed by Windows update
2. Adding registry setting DelegateSentItemsStyle with a DWORD value of 1 to HKCU\Software\Microsoft\Office\14.0\Outlook\Preferences
13 May 2012
Synchronize Project Server 2010 with Exchange 2010
A. Enable Exchange synchronization for the PWA
1. In Server Settings page in PWA, goto Operational Policies - Additional Server Settings - Exchange Server details then check on
2. Synchronize Tasks check box
B. Create a PWA user account for each CAS server
1. From Server Setting page in PWA create new user
2. Clear "User can be assigned as a resource" check box and type the name of CAS server in the Display Name field. For eg CAS_Server
3. In the User Authentication section, enter the Windows account for CAS server computer account in the User logon account field. In my case DOMAIN\CAS_Server$
4. Check on Prevent AD synchronize this account
5. In the Security group section, add the user to the Administrator group
6. Click Save button
C. Configure Project Server users for Exchange synchronization
In Server Settings page in PWA double click on each existing user and check on Synchronize Tasks check box
D. Configure impersonation permissions for the Project Server Queue Service account
1. Discover account that is running Project Server Queue service
2. Log on to Exchange server, launch Exchange Management Shell as Administrator
3. Type the below command, replace the string queuingserviceaccount with the account in step 1
Add-ADPermission -Identity (Get-ExchangeServer).DistinguishedName -User (Get-User -Identity queuingservice_account | Select-Object).identity -extendedRights ms-Exch-EPI-Impersonation
If you get the below error that means you have more than one CAS server. Please follow step 3.1
3.1 Enter the below command in Exchange Power Shell
You will get
Repeat step 3.1 on every CAS server in your Exchange farm
E. Configure impersonation persmissions for all Exchange users
Execute this command in CAS server
You will get
Name Role RoleAssigneeName RoleAssigneeType AssignmentMethod EffectiveUserName
---- ---- ---------------- ---------------- ---------------- ----------------
PRJEXCHIntegration ApplicationImp... queuingservice_account User Direct
References:
http://go.microsoft.com/fwlink/p/?LinkId=202797 (video)
http://blogs.msdn.com/b/mohits/archive/2010/05/29/integration-of-project-server-2010-and-exchange-2010-2007.aspx
http://technet.microsoft.com/en-us/library/ff468700.aspx
1. In Server Settings page in PWA, goto Operational Policies - Additional Server Settings - Exchange Server details then check on
2. Synchronize Tasks check box
B. Create a PWA user account for each CAS server
1. From Server Setting page in PWA create new user
2. Clear "User can be assigned as a resource" check box and type the name of CAS server in the Display Name field. For eg CAS_Server
3. In the User Authentication section, enter the Windows account for CAS server computer account in the User logon account field. In my case DOMAIN\CAS_Server$
4. Check on Prevent AD synchronize this account
5. In the Security group section, add the user to the Administrator group
6. Click Save button
C. Configure Project Server users for Exchange synchronization
In Server Settings page in PWA double click on each existing user and check on Synchronize Tasks check box
D. Configure impersonation permissions for the Project Server Queue Service account
1. Discover account that is running Project Server Queue service
2. Log on to Exchange server, launch Exchange Management Shell as Administrator
3. Type the below command, replace the string queuingserviceaccount with the account in step 1
Add-ADPermission -Identity (Get-ExchangeServer).DistinguishedName -User (Get-User -Identity queuingservice_account | Select-Object).identity -extendedRights ms-Exch-EPI-Impersonation
If you get the below error that means you have more than one CAS server. Please follow step 3.1
Cannot bind argument to parameter 'Identity' because it is null.
+ CategoryInfo : InvalidData: (:) [Add-ADPermission], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Add-ADPermission
3.1 Enter the below command in Exchange Power Shell
[PS]$CAS_Server = get-exchangeserver | where { $_.ServerRole -match "ClientAccess" }
[PS]$CAS_Server | foreach-object {Add-ADPermission -Identity $_.DistinguishedName -User (Get-User -Identity queuingservice_account | select-object).identity -extendedRights ms-Exch-EPI-Impersonation}
You will get
Identity User Deny Inherited
-------- ---- ---- ---------
CAS_Server DOMAIN\queuingservice_account False False
Repeat step 3.1 on every CAS server in your Exchange farm
E. Configure impersonation persmissions for all Exchange users
Execute this command in CAS server
[PS] New-ManagementRoleAssignment -Name PRJEXCHIntegration -Role applicationImpersonation -user DOMAIN\queuingservice_account
You will get
Name Role RoleAssigneeName RoleAssigneeType AssignmentMethod EffectiveUserName
---- ---- ---------------- ---------------- ---------------- ----------------
PRJEXCHIntegration ApplicationImp... queuingservice_account User Direct
References:
http://go.microsoft.com/fwlink/p/?LinkId=202797 (video)
http://blogs.msdn.com/b/mohits/archive/2010/05/29/integration-of-project-server-2010-and-exchange-2010-2007.aspx
http://technet.microsoft.com/en-us/library/ff468700.aspx
16 Jan 2012
Windows Server 2008 : Domain Name System and IPv6 - Performing Zone Transfers
Copying
the DNS database from one server to another is accomplished through a
process known as a zone transfer. Zone transfers are required for any
non-Active Directory-integrated zone that has more than one name server
responsible for the contents of that zone. The mechanism for zone
transfers varies, however, depending on the version of DNS. Zone
transfers are always pulled by the secondary servers from the primary
servers.
| ||||||||||||||||||||||||||||||||||||
1.
|
Launch Server Manager on the DNS server with the primary zone.
| |||||||||||||||||||||||||||||||||||
2.
|
Expand the Roles, DNS Server, DNS nodes, and then select the server name.
| |||||||||||||||||||||||||||||||||||
3.
|
Select the Forward Lookup Zones node.
| |||||||||||||||||||||||||||||||||||
4.
|
Right-click the name of the zone and choose Properties.
| |||||||||||||||||||||||||||||||||||
5.
|
Choose the Zone Transfers tab.
| |||||||||||||||||||||||||||||||||||
6.
|
Check Allow Zone Transfers and select Only to the Following Servers.
| |||||||||||||||||||||||||||||||||||
7.
|
Click
Edit, type in the IP address of the server that will receive the
update, and press Enter. The server will be validated, as shown in Figure 1.
Because the server is not yet an authoritative server for the zone, the
error message “The server with this IP address is not authoritative for
the required zone” appears. This will be done in the next section. The
error can be safely ignored. Click OK to save.
Figure 1. Setting up zone transfer servers.![]() | |||||||||||||||||||||||||||||||||||
8.
| ||||||||||||||||||||||||||||||||||||
9.
|
Click OK to save the changes.
| |||||||||||||||||||||||||||||||||||
1.
|
Launch Server Manager.
| |||||||||||||||||||||||||||||||||||
2.
|
Expand the Roles, DNS Server, DNS nodes, and then select the server name.
| |||||||||||||||||||||||||||||||||||
3.
|
Select the Forward Lookup Zones node.
| |||||||||||||||||||||||||||||||||||
4.
|
Select Action, New Zone.
| |||||||||||||||||||||||||||||||||||
5.
|
Click Next on the Welcome page.
| |||||||||||||||||||||||||||||||||||
6.
|
Select
Secondary Zone from the list of zone types. Secondary zones cannot be
AD-integrated and the options will be grayed out. Click Next to
continue.
| |||||||||||||||||||||||||||||||||||
7.
|
Type in the name of the zone that will be created (this should match the primary zone name), and click Next to continue.
| |||||||||||||||||||||||||||||||||||
8.
|
Type
in the IP address of the server or servers from which the zone records
will be transferred. Press Enter for each server entered, and they will
be validated. Click Next to continue.
| |||||||||||||||||||||||||||||||||||
9.
|
Subscribe to:
Posts (Atom)