2012 in review

The WordPress.com stats helper monkeys prepared a 2012 annual report for this blog.

Here’s an excerpt:

600 people reached the top of Mt. Everest in 2012. This blog got about 3,300 views in 2012. If every person who reached the top of Mt. Everest viewed this blog, it would have taken 6 years to get that many views.

Click here to see the complete report.

Procedure for Exchange 2010 DAG – Datacenter Failover

Brief

In Our Scenarios we had 10 Mailbox Server, 5 in each site & 2 Public Folder Server one in each site. We had two witnesses Server, the primary was set in DC1 and the alternate was set in DC2, so our primary Site was DC1.

This article is based on When we have Datacenter Activation Coordination Protocol is Enabled (DACP).

Step1. Ensuring that Primary DC Outage has been Declared

Ping Mailbox Server

Ping HUB Server

Ping CAS Server

Step2. Stopping the DAG from the Secondary DC for Primary DC Mailbox Server

Note:

  • Ensure that you have Full Permission on the Exchange ORG, there should not be any restriction using RBAC.
  • Before running the below command open the Exchange Management Shell “Run as administrator” otherwise the cmdlets won’t load to the PowerShell you may get an error message.
  • This has to be ran from any of the Exchange Server From the Secondary DC

Stop-DatabaseAvailAbilityGroup –identity DAG1 -Mailboxserver EXM01.contoso.com -configurationonly

Stop-DatabaseAvailAbilityGroup –identity DAG1 -Mailboxserver EXM02.contoso.com -configurationonly

Stop-DatabaseAvailAbilityGroup –identity DAG1 -Mailboxserver EXM03.contoso.com -configurationonly

Stop-DatabaseAvailAbilityGroup –identity DAG1 -Mailboxserver EXM04.contoso.com -configurationonly

Stop-DatabaseAvailAbilityGroup –identity DAG1 -Mailboxserver EXM05.contoso.com –configurationonly

Step3. Stopping the Cluster Service on every DAG-Member of the secondary data-center

Note:

You might see sometime it will result that Cluster Service is already stopped, but no, check using the Services Console, Ensure Cluster Service is in stopped state.

Net stop clussvc

Step4. Reactivate the mailbox-servers in the standby data

Restore-databaseavailabilitygroup –identity DAG1

Note:

Most of the time you will see database will start mounting after executing this command successfully, and also this will start the cluster service on all the DAG members in the secondary DC. If this happens so then skip the step 5, if cluster service has not started perform the step.

Step5. Starting the Cluster Service on every DAG-Member of the secondary data-center

Net start clussvc

or

Open the services console and choose the Cluster Service and start it.

Step6. All the DB should be mounted to the respective Secondary DAG members

Note:

All the DB should be switched to the respective DAG member successfully. If mailbox-databases don’t switch automatically run the script to move databases to passive

Resume-MailboxDatabaseCopy ‘DATABASENAME\SERVERNAME’

or

Mount-Database -Identity ExchangeServerFQDN\DatabaseName

Step7. Check the Status of the DB

Check the DB Copy Status and Ensure they all are healthy. In My Case I had DB Created with Standard Name DB1 to DB72, So I used the below PowerShell to check the copy of all in one shot.

Get-MailboxDatabaseCopyStatus -Identity DB* | select name, status, SelectcontentIndexState | sort Status | ft –auto

Note:

Mount the databases if not done automatically.

Step8. Move OAB Generation to to Secondary Site Public Folder Server

Move-OfflineAddressBook -Identity “Offline Address Book” -Server EXP11

Step9. Do the Final check for Functionalities i.e.

Note:  

While accessing the Public Folder using Outlook you might see the outlook hanging but that’s ok, you can ignore it as once the connection get thru with new Public Folder Server, you won’t find the slowness.

  • Email Flow (Internal/External):
  • PUB Folder Access 
  • ActiveSync:
  • All DB: Mounted
  • Free/Busy:
  • OAB:
  • OWA:
  • POP3:
  • IMAP:
  • Blackberry:

Step9. Primary DC Switchback Steps

Note:

You got to know that the Network Connectivity has been resumed to the primary DC.

Also ensure that you got the final instruction that to proceed with Primary Datacenter Restore for exchange.

Ping Primary Mailbox Server

Ping Primary HUB Server

Ping Primary CAS Server

Step10. Ensure Cluster service has been started on Primary Datacenter Server, if not start it

Note:

You will see that Cluster Service is in Disabled state on all the Primary Datacenter in most cases the cluster service won’t start 

First enable the service by going to services.msc console and then start it

Or

Net start clussvc

If you are getting the error while starting the Cluster Service, then we need to perform cleanup by running the below command.

 

 

Cluster Node EXM01.contoso.com /forcecleanup

Cluster Node EXM02.contoso.com /forcecleanup

Cluster Node EXM03.contoso.com /forcecleanup

Cluster Node EXM04.contoso.com /forcecleanup

Cluster Node EXM05.contoso.com /forcecleanup

Step11. Start the DAG for all the Failed Server

Start-DatabaseAvailabilityGroup -MailboxServer EXM01.contoso.com

Start-DatabaseAvailabilityGroup -MailboxServer EXM02.contoso.com

Start-DatabaseAvailabilityGroup -MailboxServer EXM03.contoso.com

Start-DatabaseAvailabilityGroup -MailboxServer EXM04.contoso.com

Start-DatabaseAvailabilityGroup -MailboxServer EXM05.contoso.com

Step12. Then run the below command from any of the Exchange server

Set-DatabaseAvailabilityGroup –Identity DAG1

Step13. Move the OAB Generation server back to the EXP01 as it was earlier

Move-OfflineAddressBook -Identity “Offline Address Book” -Server EXP01

Step14. Redistribute the Mailbox Database copy across the Primary and Secondary DC

Note:

Ensure all the DBs are mounted and second copies are in health state.

Ensure all the nodes are up and showing good in the Failover Cluster Manager

In My Case I used mine one. You Can use your Own Script to Distribute The DB

Step15. Check all the functionalities

  • Email Flow (Internal/External)
  • PUB Folder Access:
  • ActiveSync:
  • All DB: Mounted
  • Free/Busy:
  • OAB:
  • OWA:
  • POP3:
  • IMAP:
  • Blackberry:

 Cheers,

Planning Exchange 2010 Deployment Project

One of the Crucial part before executing any project is Planning, Which is really hard when it comes to Designing a Solution for a kind of  Quite Complex Scenarios.

I was going thru few articles but cant find the detailed one, but finally i referred one book Exchange 2010 Best Practices written by Siegfried Jagott & Joel Stidley

It gives you the complete picture about your Exchange 2010 Project Planning, This is completely based on MOF as well as this also talks about live experience.

As per the Microsoft Operation Framework there is four layers Called “Plan, Deliver, Operate and the operation layer called Manage.

This Exchange Project Plan has touched the each layer of Microsoft Framework, Which talks what are do we need to do when as this is important to know about each of this and what we should talk about.

Plan

In this we are mostly going to ask question with client or gather information in the first meeting.

Business Question

  • What are the organization’s strategic business objectives?
  • What are the budgetary goals for these types of projects ?
  • Are there any internal business roadblocks that could cause delays or objectives to the business requirements?
  • Do any internal business processes or departments need extra attention to ensure the success of the project ?
  • Which tasks should be handled by current IT staff, consultants, or other outsourced resources?
  • What are the business reasons for adopting the particular technology?
  • Are there business drivers for the migration or for the new implementation or technology?
  • What industry-specific system requirements are needed ?

Technical Question

  • What are the most important technology goals and objectives for your organization?
  • What are the service-level requirements the messaging system and related services should meet?
  • What are the functional requirements for the messaging system?
  • Which IT skills and resources are strategic to the organization?
  • Which tools and third-party applications need to be included in the design?
  • How many users need to be included and where are they located?

Deliver

MOF includes five main steps in this phase: Envision, Project Planning,
Build, Stabilize, and Deploy. But as per real experience this has stretch with four more steps.

Envision

  • Step 1: Envision: Identify business and technical requirements.
  • Step 2: Assess.
  • Step 3: Evaluate the new solution(s) and potential designs.
  • Step 4: Build a proof of concept.
  • Step 5: Create a design.

Project Planning

  • Step 6: Develop the deployment and obtain buyoff.

Build/Stabilize

  • Step 7: Implement a pilot. Begin pilot, adjust the plan, and complete deployment.

Deploy

  • Step 8: Deploy.
  • Step 9: Post-implementation review

Step 1: Envision:

  • 1.1 Service and Organizational Level Agreements (SLAs or OLAs)
  • 1.2 Operational costs
  • 1.3 Network costs
  • 1.4 Backup and restore cost and performance improvements
  • 1.5 Improved provisioning processes (for example, HR Systems)
  • 1.6 Exchange enhancement that enables larger mailboxes
  • 1.7 Reducing licensing costs
  • 1.8 Return on investment (ROI) and budgetary considerations
  • 1.9 Data retention and isolation
  • 1.10 Auditing and compliance requirements
  • 1.11 Message archiving requirements
  • 1.12 Antivirus and anti-spam functionality
  • 1.13 Client access
  • 1.14 Security requirements
  • 1.15 Line-of-business application integration
  • 1.16 Performance planning
  • 1.17 Capacity planning and management

Step 2.Assess :

  • 2.1 Identify and prioritize currently deployed applications by how crucial they are to business functionality.
  • 2.2 Identify the clients that are currently in use.
  • 2.3 Document service-level and organizational-level agreements in place.
  • 2.4 Inventory the hardware currently in use.
  • 2.5 Document the network infrastructure design.
  • 2.6 Identify where the messaging servers are currently located, the number and size of local mailboxes and public folder replicas, and the number and average size of the e-mail messages sent and received.
  • 2.7 Identify the Active Directory Domain Services (AD DS) configuration.
  • 2.8 Update any messaging configuration documentation to ensure that all data needed to complete a project plan is available.
  • 2.9 Identify the people involved in managing Exchange and all of the dependent services.
  • 2.10 Perform a risk assessment
  • 2.11 Document the executive escalation path.

Step 3: Evaluate the new solution(s):

  • 3.1 Here you Evaluate the Product (Software & Hardware)
  • 3.2 Looks about the Feature which would require for the clients
  • 3.3 Third Party Prducts (Antivirus, Mobility, Archival)

Step 4: Build a proof of concept:

  • 4.1 Prepare :

Verifying functionality is critical in the test environment.
This testing allows time to verify assumptions, verify
functionality, and create a detailed and accurate
deployment design. This is also a good time to learn
more about the product. To prepare for this work, gather
all of the software, hardware, and configuration guides that
are being considered for use in the design.

  • 4.2 Deploy Proof of Concept:

Deploy an isolated test environment that is as close as
possible to the expected production environment and
allows testing to be completed. Testing in this phase should
include potential migration scenarios.

  • 4.3 Test :

Perform the test scenarios and note the detailed results. Be
sure to note any changes to the test scenarios
because of new or changed features.

  • 4.4 Review Test Results:

After the testing is completed, the issues and potential
changes should be reviewed. The reasons for any
unexpected results should also be captured. For instance,
did the test fail because a feature or function didn’t work as
expected, or were there limits reached?
The review should categorize each issue’s criticality and
then each issue should be addressed by changing the
design, opening support cases with the appropriate
vendors, or adjusting the current process to accommodate
the new functionality. Any user behavioral changes should
be documented and later clearly communicated to the
affected users.

Step 5: Create a Design

  • 5.1 Define Client Standards
  • 5.2 Define Network and Security Designs
  • 5.3 Define Antivirus and Anti-spam Design
  • 5.4 Define Application Compatibility and Integration
  • 5.5 Define Infrastructure Changes
  • 5.6 Define and Re mediate Risks
  • 5.7 Develop Communication Plan
  • 5.8 Develop Marketing and Training Plan
  • 5.9 Define Migration Process

Step 6: Develop the deployment and obtain buyoff.

  • 6.1 Create Design Milestones
  • 6.2 Obtain Project Resources
  • 6.3 Define Education and Training Requirements and Communications Plan
  • 6.4 Obtain Executive Buy-in

Step 7: Implement a pilot. Begin pilot, adjust the plan, and complete deployment.

  • 7.1 Pilot Planning
  • 7.2 Implement the Core Exchange 2010 Infrastructure
  • 7.3 Pilot Deployment
  • 7.4 Evaluate the Pilot Process
  • 7.5 Pilot Evaluation

Step 8: Deploy:

  • 8.1 Create Migration Plan and Schedule
  • 8.2 Complete Deployment Communication and Training
  • 8.3 Implement the Exchange 2010 infrastructure
  • 8.4 Perform Migration

Step 9: Post-implementation review:

  • 9.1 Operate
  • 9.2 Operations
  • 9.3 Service Monitoring and Control
  • 9.4 Customer Service
  • 9.5 Problem Management

At Last the its Manage where you can take care for these Points.

Manage

Governance, Risk, and Compliance

Change and Configuration Management

Process Improvement and Management

Cheers,

Ashwini Kumar

 

How to:Re-seed Failed Mailbox Database Copy in Exchange Server 2010

As you can see here DB030 shows as Failed for DAG Member EXM15, to get this fixed we have to reseed the DB.

Step1: Suspend the Failed DB by executing the below command 

Suspend-MailboxDatabaseCopy -Identity “B030/EXM15”

This will ask your confirmation to perform the Suspend for this DB/Server, Select A [Yes to all]

As you can see below

 Step2: Update the Failed Mailbox DB copy from the Active one, by running this shell and Make resume it.

Update-MailboxDatabaseCopy -Identity “B030/EXM15” –DeleteExistingFiles

Note: The duration of the seeding process will depend on the size of the database and the speed of the network. When the update has completed it will automatically resume replication for the database copy.

Just in case if you want the replication to resume it manually use the below command.

Update-MailboxDatabaseCopy -Identity “B030/EXM15” -DeleteExistingFiles -ManualResume

Blackberry mail flow in various scenarios

Architecture: Blackberry Enterprises Solution                        

The Blackberry Enterprises Solution has been got used using this component. This is the standard architecture of data flow between the Blackberry devices to Messaging server.

Component Description

BlackBerry device: The BlackBerry device provides  Access to email messages, calendar, Contacts, Enterprises Global Address Lookup

 Wireless network: The wireless network routes the data to and from the BlackBerry devices to the Internet through the BlackBerry Infrastructure.

 BlackBerry Infrastructure: The BlackBerry Infrastructure is designed to provide a highly secure and reliable connection to wireless networks operated by

many service providers around the world. 

Internet: The internet component is not mentioned here, however this is very much require to transport the data Internet transports data between the wireless network and the firewall.

 Firewall: The BlackBerry Enterprise Server maintains an outbound-initiated, bidirectional connection through port 3101 on the firewall and over the Internet to the BlackBerry Infrastructure.

Introducing the BlackBerry Enterprise Solution

BlackBerry Enterprise Server:

The BlackBerry Enterprise Server is installed on a computer behind the organization’s firewall. The BlackBerry Enterprise Server is designed to

 • Manage the wireless transfer of data to and from the BlackBerry devices

• Encrypt all data that flows to and from the BlackBerry devices

• Allow highly secure push delivery of content to the BlackBerry devices

 Messaging server:

The BlackBerry Enterprise Server integrates with the following messaging servers to provide wireless delivery of email messages and organizer data

• Microsoft Exchange

• IBM Lotus Domino

• Novell GroupWise

 Instant messaging server:

The BlackBerry Enterprise Server integrates with the following types of instant messaging servers to allow highly secure, wireless delivery of instant messages and data:

 • Microsoft Office Communications Server

• Microsoft Office Live Communications Server

• IBM Lotus Sametime

• Novell GroupWise Messenger

 Application or content servers:

 The organization’s application servers or content servers provide push applications and intranet content that the BlackBerry Enterprise Server makes available to the BlackBerry Devices.

Email flow for the BlackBerry Internet Service

This below design we have outlined for the email flow when a blackberry device sends emails to another Blackberry device using Blackberry internet service.

1.      An email message is sent from a BlackBerry smartphone. The email message is compressed so that it is in CMIME format and sent to the wireless network.

2.      The wireless network delivers the email message to the BlackBerry Infrastructure.

3.      The BlackBerry Infrastructure uses the UID field in the [CMIME] service book to deliver the email message to the appropriate BlackBerry Internet Service server.

4.      The BlackBerry Internet Service converts the email message to standard MIME format and sends the email message to the Internet. The email message is sent through the Internet using SMTP to the recipient’s messaging server.

5.      Then the messages reaches to the recipient users, Then once the recipient replies to that email, the data flow happens as mentioned below.

6.      An email message is sent to the BlackBerry smartphone user from an email application on the computer. The email message is delivered through the Internet to the BlackBerry Internet Service.

7.      The email message is compressed by the BlackBerry Internet Service so that it is in CMIME format and sent to the BlackBerry Infrastructure.

8.      The BlackBerry Infrastructure sends the email message to the wireless network using the current assigned PIN.

9.      The email message travels over the wireless network to the BlackBerry smartphone which decompresses the email message.

 Email flow for the BlackBerry Professional

The below outline shows – the email data flow in the infrastructure of Blackberry Professional & Messaging server.

1.      BlackBerry smartphone User A creates an email message and Sends it. The email message is compressed, encrypted, and sent to the wireless network.

2.      The wireless network sends the email message to the Internet through the BlackBerry Infrastructure.

3.      The email message reaches the firewall, where it passes through an outbound-initiated, two-way connection to the BlackBerry Professional Software.

4.      The BlackBerry Professional Software decrypts the email message, decompresses it, and places it in BlackBerry smartphone User A’s outbox.

5.      The messaging server forwards the email message to the recipient in the organization.

6.      The BlackBerry Professional Software monitors User B’s mailbox and retrieves the new email message. The new email message is applied against global and personal email message filters. If the email message is being sent to BlackBerry smartphone User B’s BlackBerry smartphone, the BlackBerry Professional Software compresses and encrypts the first 2 KB of the email message and queues it for delivery.

7.      The email message is sent by the BlackBerry Professional Software through an outbound-initiated, two-way connection on the firewall to the Internet.

8.      The email message is sent through the Internet to the organization’s firewall.

9.      The email message arrives at User B’s mailbox.

Email Message flow for the BlackBerry Enterprise Solution

Email messages sent to and from BlackBerry smartphones the following scenario outlines the email message flow when an email message is sent by a BlackBerry smartphone user in one organization

(BlackBerry smartphone User A) and received by a BlackBerry smartphone user in another organization (BlackBerry smartphone User B) through the BlackBerry Enterprise Solution

1.  BlackBerry smartphone User A creates an email message and sends it. The email message is compressed, encrypted, and sent to the wireless network.

2.      The wireless network sends the email message to the Internet through the BlackBerry Infrastructure.

3.      The email message reaches the firewall where it passes through an outbound-initiated, two-way connection to the BlackBerry Enterprise Server.

4.      The BlackBerry Enterprise Server decrypts the email message, decompresses it, and places it in BlackBerry smartphone User A’s outbox.

5.      The messaging server sends the email message as SMTP traffic through the firewall using the port designated for email messages.

6.      The email message travels across the Internet as SMTP traffic and arrives at BlackBerry smartphone User B’s firewall.

7.      The firewall allows the email message to pass through to the messaging server, where it is placed in BlackBerry smartphone User B’s mailbox.

8.      The BlackBerry Enterprise Server monitors BlackBerry smartphone User B’s mailbox and retrieves the new email message. The new email message is applied against global and personal email message filters. If none of the filters apply to the email message, the BlackBerry Enterprise Server prepares to deliver it to BlackBerry smartphone User B’s BlackBerry smartphone. The BlackBerry Enterprise Server compresses and encrypts the first 2 KB of the email message and queues it for delivery.

9.      The BlackBerry Enterprise Server sends the email message through an outbound-initiated, two-way connection on the firewall to the BlackBerry Infrastructure.

10.    The BlackBerry Infrastructure sends the email message to the wireless network.

11.   The wireless network receives the email message and forwards it to BlackBerry smartphone User B’s BlackBerry smartphone.

12.   BlackBerry smartphone User B’s BlackBerry smartphone receives, decrypts, and decompresses the email message. BlackBerry smartphone User B’s BlackBerry smartphone also sends a confirmation notification to the BlackBerry Enterprise Server to indicate that the email message has been received.

Email sent to and from BlackBerry smartphones in the same ORG

The following scenario outlines the email message flow when an email message is created and received by BlackBerry smartphone users (BlackBerry smartphone User A and BlackBerry smartphone User B) in

the same organization through the BlackBerry Enterprise Solution.

1.      BlackBerry smartphone User A creates an email message and sends it. The email message is compressed, encrypted, and sent to the wireless network.

2.      The wireless network sends the email message to the Internet through the BlackBerry Infrastructure.

3.      The email message reaches the firewall, where it passes through an outbound-initiated, two-way connection to the BlackBerry Enterprise Server.

4.      The BlackBerry Enterprise Server decrypts the email message, decompresses it, and places it in BlackBerry smartphone User A’s outbox.

5.      The messaging server forwards the email message to the recipient in the organization.

6.      The BlackBerry Enterprise Server monitors BlackBerry smartphone User B’s mailbox and retrieves the new email message. The BlackBerry Enterprise Server checks the global and personal email message filters. If none of the filters apply to the email message, the BlackBerry Enterprise Server prepares to deliver it to User B’s BlackBerry smartphone. The BlackBerry Enterprise Server compresses and encrypts the first 2 KB of the email message and queues it for delivery.

7.      The BlackBerry Enterprise Server sends the email message through an outbound-initiated, two-way connection on the firewall to the BlackBerry Infrastructure.

8.      The BlackBerry Infrastructure sends the email message to the wireless network.

9.      The wireless network receives the email message and forwards it to BlackBerry smartphone User B’s BlackBerry smartphone.

10.   BlackBerry smartphone User B’s BlackBerry smartphone receives, decrypts, and decompresses the email message. BlackBerry smartphone User B’s BlackBerry smartphone also sends a confirmation notification to the BlackBerry Enterprise Server to indicate that the email message has been received.

Note:  To made this Blackberry Flow Design – I had prepard the VISIO Stencils, using that i made it. I will be posting those stencial & the softcopy of the VISIO Diagram, which i have prepared.

 

Delete old Blackberry Enterprise Server (BES) logs folder using vbscript

Scenarios :
While working daily on ticket, You have lots of stuff to work on, in Between you got a mail from Monitoring Team saying that, Team the disk space got full for log drive on one of the BES servers. On top of it your Lead asks – cant you guys put one script to do the automation here.

So finally here is that automation, which is gonna to delete old date logs automatically (Its all up to you for how many days you wanted to retain)

Solution:
=======================================
Examples:

This command will move logs older than 7 days from the folder “C:\Scripts\logs” where folder name value only contains numbers like “21112010″.

cscript //NoLogo c:\scripts\deleteBESLogFolders.vbs “C:\Scripts\logs” 7 move>> c:\scripts\BESLOg_Folder_Delete.log

This command will delete logs older than 7 days from the folder “C:\Scripts\logs” where folder name value only contains numbers like “21112010″.

cscript //NoLogo c:\scripts\deleteBESLogFolders.vbs “C:\Scripts\logs” 7 delete>> c:\scripts\BESLOg_Folder_Delete.log

——————————————————————————————————————————————————-

‘Copy and paste all the text below and create deleteBESlogFolders.vbs file.

‘Script: deleteBESlogFolders.vbs
‘Created By: Manish Girdhar
‘Date: 26 Nov 2010
‘Purpose: To delete/move folders from given path and all subfolders below this folder
‘ Usage: cscript DeleteBESlogFolders.vbs {DriveLetter:\FolderName} {#ofDays} {Delete or Move}
‘ or: cscript DeleteBESlogFolders.vbs {\\servername\FolderName} {#ofDays} {Delete or Move}
‘ Usage: cscript DeleteBESLogFolders.vbs c:\BES\log 3 d
‘ (deletes folders older than 3 days from the \BES\log file on drive C:)
‘Usage: cscript DeleteBESLogFolders.vbs c:\BES\log 3 m
‘ (moves folders older than 3 days from the \BES\log file on drive C: to C:\BES_Log_Backup)

Const BACKUP_FOLDER = “C:\BES_Log_Backup” ‘Change path folder to move log files
creatfold
Set ObjUsrInput = WScript.Arguments
FolderName =ObjUsrInput(0)
Days=ObjUsrInput(1)
Action=LCase(ObjUsrInput(2))
’1
if action = “delete” or action = “move” or action = “d” or action = “m” then
set fso = createobject(“scripting.filesystemobject”)
set folders = fso.getfolder(FolderName)
datetoday = now()
wscript.echo “”
wscript.echo “”
wscript.echo “”
wscript.echo “”
newdate = dateadd(“d”, Days*-1, datetoday)
wscript.echo “Current Date (Today):” & now()
wscript.echo “==================================================================”
wscript.echo “STARTING: Folders where date created is older than date :” & newdate & ” Will be deleted / Moved.”
wscript.echo “<>”
wscript.echo “”
route folders
wscript.echo “”
wscript.echo “COMPLETED: All Folders created older than date :” & newdate & ” are deleted / Moved.”
wscript.echo “<>”

‘=== Route Function Defined
sub route( byref folders)
set subfolders = folders.subfolders
‘==== For loop started
for each folder in subfolders
wscript.echo “”
‘Check if Date is in limit
if folder.datecreated < newdate then
””check if folder name is numeric
if IsNumeric(folder.Name) = true then
‘==============================M
”if action is MOve
if action = “move” or action = “m” then
wscript.echo “__________________________________________________________________________”
wscript.echo “Move folder :” & folder.path
wscript.echo “”
folder.move BACKUP_FOLDER & “\” & folder.Name
‘track if error
if err 0 then
DisplayErrorInfo
else
wscript.echo “”
wscript.echo “Folder Moved :” & folder.path
wscript.echo “__________________________________________________________________________”
end if ‘ tracking error
end if
‘================================M
‘End if Action is Move
‘===================== D
‘if Action is delete
if action = “delete” or action = “d” then
dim foldpath
wscript.echo “__________________________________________________________________________”
foldpath = folder.path
wscript.echo “Deleting folder :” & foldpath
wscript.echo folder.path
folder.delete
if err 0 then
DisplayErrorInfo
else
wscript.echo “”
wscript.echo “Folder Deleted :” & foldpath
wscript.echo “__________________________________________________________________________”
end if
End if
‘End of action Delete
‘======================D
End if
end if
on error resume next
next
‘====== for loop ended
set subfolders = nothing
set files = nothing
end sub
”’Function Route Ended
Else ’1

wscript.echo “Correct Action type not defined”

End if ’1

Sub DisplayErrorInfo
WScript.Echo “Error: : ” & Err
WScript.Echo “Error (hex) : &H” & Hex(Err)
WScript.Echo “Source : ” & Err.Source
WScript.Echo “Description : ” & Err.Description
Err.Clear
End Sub

sub creatfold
dim objFSO
set objFSO = createobject(“Scripting.FileSystemObject”)
if objFSO.FolderExists(BACKUP_FOLDER) then
else
objFSO.CreateFolder(BACKUP_FOLDER)
end if
End sub

Note: The Content has been taken from one of my favorite Blog title

Unable to Sync the Blackberry Contact field (Mobile 2) in MS Outlook

Issues :

one Day we came across with case, where a high profile users were loose lots of contacts & after checking with them we found “User’s Blackberry Device were not able to sync the Contact field (Mobile 2) from the Blackberry to MS Outlook.

Solution

There has no solution made so far, User has to save all the mobile 2 option to diffrent category, i.e Business No, Home No etc.

Note : Even the same issues happens with Nokia as well, why becasue in outlook we dont have the field for Mobile 2.

Unable to attach the file from the media card using emails on model 9800 Blackberry Torch Device.

Problem : User is not able to attach the file from the media card using emails on model 9800 Blackberry Torch Device.

“we found user device was content protection enabled, which usually organization use to protect the device, Specially this issues we came across to 9800 models only.

Workround : Just disabled the mdeia card encryption by going to the Media card properties.

Solution : This has been fixed in 6.0.0.287 (Bundle 870) and above. AT&T is not yet released the device software version 6.0.287 and users are required wait until the update is available.