Thursday, August 21, 2014

How do I install a network printer for all users on a Windows 7 computer?

     
When you add a printer as a local printer all user can view it.
 
In Windows XP:
  1. Click Start > Printers and Faxes.
  2. Click Add a Printer on the left pane.
  3. Click Next.
  4. Select Local printer attached to this computer and click Next.
  5. Select Create a new port, select Local Port for the Port Type, and click Next.
  6. For Port Name, enter the network path to the printer by entering two slashes, the computer name or local IP address of the PC sharing the printer, and then the share name of the printer. For example “\\dellpc\hpprinter” or “\\192.168.1.100\hpprinter”
  7. Select the printer and click Next. If the exact model isn’t listed, try the closest model number or a generic printer.
  8. Follow the rest of the wizard.
In Windows Vista and 7:
  1. Click Start > Devices and Printers.
  2. Click Add a Printer on the top.
  3. Select Add a local printer.
  4. Select Create a new port, select Local Port for the Port Type, and click Next.
  5. For Port Name, enter the network path to the printer by entering two slashes, the computer name or local IP address of the PC sharing the printer, and then the share name of the printer. For example “\\dellpc\hpprinter” or “\\192.168.1.100\hpprinter”
  6. Select the printer and click Next. If the exact model isn’t listed, try the closest model number or a generic printer.
  7. Follow the rest of the wizard.       

Courtesy : http://www.windowsnetworking.com
Monday, August 18, 2014

SpeedNet Version 4.2 Release Date 16.06.2014

Purpose of release:

Release of Version 4.2 is necessitated due to the following update requirements:

i.                     Introduction of Direct Bagging for Bulk Addressees from origin Sorting and IC Hubs.

ii.                   Handling of new barcode series with prefix ‘PP’ to allocated to Passport articles.

iii.                  Requirement to allow Prepaid/Advance customers to book SP-COD articles.

iv.                 New requirements and bug fixes as detailed in the ‘New Features’ section of this document.

Further, SpeedNet Communication is now equipped with additional ability to download & perform auto-upgrade for SpeedNet versions, new scripts and office master files from a single location on SpeedNet Central Server. This is an additional facility to the feature made available in Speednet Communication 4.1, which facilitated pushing of Speednet Version 4.1.1 from Speednet Central Server.

The beta version of Speednet 4.2 was under testing at various field locations and pan-India release made on 16.08.2014.

This document covers the new features and bug fixes done in following versions viz.,

1)      SpeedNet 4.0 Release Date 10.06.2013 (Test version for SP-COD)

2)      SpeedNet 4.0 Release Date 12.09.2013 (Pan-India release for SP-COD)

3)      SpeedNet 4.1 Release Date 31.10.2013

4)      SpeedNet 4.1.1 Release Date 02.12.2013

Index:


I.    a)      New Features / options
      b)      Bugs Fixed          

II.           Pre-requisites

III.          Fresh Installation / Upgradation procedure

IV.          Things to do - check list

V.           Feed back / Error reporting

 
I.       New Features / options:

The following new options are included in SpeedNet 4.2 Release dated 16.06.2014:

1)      Direct Bagging for Bulk Addressee from Sorting Hubs / IC Hubs:

In Operator login under ‘Bulk Delivery’ menu, new option ‘Direct Bag from other Hub/ICH invoicing’ is available for Sorting Hubs / IC Hubs.  The operational guideline on bagging for Bulk Addressees is supplied separately.

2)      New prefix ‘PP’ has been allocated for booking of Passports vide MB Division, Directorate lr.no.  30-35/2013-D dated 13.08.2014.

The new prefix will now be allowed for booking and delivery operations in Speednet Version 4.2.

3)      SP-COD booking facility made available to Prepaid/Advance customers.

SP-COD booking facility was available to BNPL category, which is now extended to Prepaid/Advance customers.

4)      Report on SPAs invoiced to BOs pending for Returns beyond seven days and thirty days:

An alert during Supervisor and Operator login and a report on SPAs invoiced to BOs pending for Returns beyond seven days and thirty days:

During each Supervisor and Operator login, an alert message will appear if SPAs invoiced to BOs are pending for returns beyond seven days.

To get details of such SPAs, Supervisor / Operator can use Reports à Other Reports à BO Returns Pending Beyond Seven Days option.

5)      Taking returns of SPAs invoiced to BOs is not allowed beyond 30 days:

Taking returns of SPAs invoiced to BOs is restricted to 30 days period under Delivery à Speed Post Articles à Remarks From Other Offices option.

6)      SpeedNet Communication - ability to download new version files, scripts, office master files:

Speednet Communication has now got the ability to download new version files, scripts, office master files, etc from a single location on Speednet Central Server and perform auto-upgradation without any manual intervention.
 
This is an additional facility to the feature made available in Speednet Communication 4.1, which facilitated pushing of Speednet Version 4.1.1 from Speednet Central Server.

7)      SpeedNet Communication - updation of Branch Office Master Data with new Message file:

Updation of Branch Office Master Data through SpeedNet Communication with new Message file.

8)      SpeedNet Communication – Supervisor and Operator will get alert when messages found not transmitted from EMSClient folder.
 
The following new options were included in SpeedNet 4.1 Release dated 31.10.2013:

1)      RTS / Missent remark is made mandatory for despatching of SPAs in Post Offices

2)      Provision to select delivery date while taking returns for delivered Bulk Addressee SPAs under Bulk Delivery option for SH / ICH

3)      Bulk Addressee Special Delivery Manifest is redesigned to accommodate three SPAs per row

4)      Updation of remarks for Articles under “Other Office Articles – Delivery Data” option is limited to PIN code jurisdiction of respective Post Office

5)      Provision to upgrade local databases from Central Server through SpeedNet Communication

The following new options were included in SpeedNet 4.0 Release dated 12.09.2013:

1)     Speed Post - Cash on Delivery (SP-COD):

BD & M Directorate has formulated the SP-COD scheme for customers, who place the orders for goods through mail order / on phone and make payment at the time of delivery of articles.

For the purpose of SP-COD, special barcode series has been allotted to M/s. Amazon.com for Speed Post viz., ‘AW’ series and ‘AC’ series for cash on delivery articles. As such, SPAs with ‘AC’ series barcode are treated as cash on delivery SPAs.

For more information on SP-COD and its applicability, please read SOP on SP-COD. Features of SP-COD are detailed in the PPT.


BD & M Directorate has introduced the BRSP scheme for merchants / retail service providers, who wants a service which enables customers, who are either not satisfied with the product received or receives the product in damaged condition, to send back the merchandise to merchants / retail service providers at no cost.

For the purpose of BRSP, special barcode prefix viz., ‘BR’ is used. As such, SPAs with ‘BR’ series barcode are treated as BRSP articles.

For more information on BRSP and its applicability, please read SOP on BRSP.


This option is meant for delivery of SPAs directly from Sorting / IC Hubs to Bulk Addressees and taking returns for such SPAs.

The ‘Bulk Delivery’ menu is available only for Sorting Hubs / IC Hubs instead of ‘Delivery’ menu, which is available only for offices other than Sorting Hubs / IC Hubs.

Initially, Bulk Delivery menu will be disabled for Operators in Sorting Hubs / IC Hubs, which needs to be enabled by selecting the menu options, ‘Bulk Delivery Invoicing’, ‘Bulk Delivery Returns’ and ‘Request Bulk Addressee Data’ under Supervisor à Master à Duty Allocation à Modify option.


Requirement received from field units for provision to update the delivery information of RGI articles for which delivery returns are already taken, but shown as undelivered on RGI MIS and same has been provided.


Provision has been made available in SpeedNet 4.0 for regeneration of Delivery messages for which delivery data is available in the local system. This option can be used to update delivery data in respect of RGI articles so that the RGI MIS is updated with delivery information.

The option is available under Supervisor à Tools à Resend Booking & Delivery Data.

6)     International EMS tariff revision w.e.f. 01.05.2013:

International EMS tariff revision was effected w.e.f. 01.05.2013, which is now included in SpeedNet 4.0. The update for tariff revision was provided till now only on request.
 

In view of data integrity especially in respect of SP-COD articles, which involve financial aspects, encryption policy has been adopted in SpeedNet communication.


SpeedNet Communication now has the capability to upgrade databases without the implicit use of Meghdoot Scripter (ScriptTool.exe). Any EXL file received from CEPT can be copied to the Data folder in the RXD folder of EMSClient for further processing.


Office Master data will be pushed from SpeedNet Central Server on a periodic basis and the same will be updated through SpeedNet Communication.

However, the option to update the Office data implicitly by downloading Office Master file from SPC Office Configuration site is retained for the benefit of SpeedNet offices.


In accordance with the orders received from Directorate the following modification has been done in Delivery à Returns option, Remarks from other offices option and Delivery Other Office Articles - Delivery Data option:

a)    A Provision is made under Delivery à Remarks from other offices option to enter the time of delivery.

b)   Uniformity in showing the current date and time is made across all the returns option.

c)    In case if actual time of delivery is not entered, then local system time at the time of taking returns / uploading delivery information will be taken as time of delivery.



A new report based on the requirements of BD & M Directorate for Speed Post MIS – Delivery Performance is included under Supervisor à Reports à Other Reports à Speed Post Delivery Incentive option.

Note:

Delivery data is retained in the POSPCC database for 45 days only. Hence, the Speed Post MIS - Delivery Performance Report needs to be generated / printed within 15 days from the completion of month.


For WNX articles booked in Meghdoot Point of Sale module, booking data for the WNX articles is fetched along with other Speed Post articles and collection of WNX articles can be done in SpeedNet. After collection WNX articles can be closed using the option provided under Operator à Issues à Closing of WNX Bag. Bag closing and despatch process for WNX bag is same as that of other Speed Post bags.


A single point installation / upgradation to SpeedNet 4.0 is implemented through use of “SpeedOne Installer.exe” and “SpeedOne Updater.exe” doing away the need for individual installation / upgradation process in vogue for the previous versions.

Bugs fixed:


1)        Booking of SP-COD articles using ‘EZ’ series in offices having more than one SP-COD customer (with different barcode range)

2)        Allowing invoicing of foreign articles with ‘EZ’ series to beat / postman

3)        Office Configuration issue during fresh installation

4)        BNPL Monthly Bill Report display billing amount of more than 6 digits

5)        Office Master updation in SpeedNet Communication (Bulk Upload error, invalid data error etc.,)

6)        Handling of unprocessed files lying pending in SpeedNet Communication folders due to various reasons


1)      Provision to Auto-save the articles invoiced in the Bulk Addressee option for Post Offices

2)      Calculation of taxes updated for Prepaid/Advance Customers at the time of monthly billing

3)      Issues relating to database configuration noticed during fresh installation have been rectified

The following bugs were fixed in SpeedNet 4.0 Release dated 12.09.2013:

1)      Error while modifying remarks under Remarks From Other Offices option

2)      Mandatory requirement for scanning of Missent articles under Delivery à Dispatch à Missent Articles option is enforced

3)      Closing of SP Bags error: SQL Server Deadlock issue

4)      Constraint in repeated handling of same article in receipt and disposal

5)      Virtual Scanning (opening of bag / receipt of articles) issues

6)      Errors in opening of Transit bags and bundles

7)      Errors during modification of bags opened including transit bags

8)      Fetch from counter issues: Collation errors, Heterogeneous query errors, SQL 2005 and 2008 related errors

9)      Abstract related issues

10)   Discrepancy report modified to segregate articles collected and not disposed, articles received but not disposed

11)   Configure Mail List error for offices like MBC, BNPL etc.,

12)   Flush Data Logic change to speed up the flushing process

13)   New concept of active status for offices implemented for excluding old offices data during bag receipt / open/ close options etc.,

14)   Post Paid / Advance customer billing logic modified to exclude discount on tax values

15)   Extension of period of retention of delivery data


1)        Hardware: 

Mininum Pentium IV CPU with 2GHz speed,

1GB RAM and

1 GB free Hard Disk space.

2)        Operating System:

Minimum Windows XP SP2 or higher.

3)        Database: 

Minimum SQL Server 2000 or higher.

4)     Application Software:

a)            SpeedNet Server Version 3.1.

b)           

(i)     SpeedNet Client Version 3.1.2 Update 6 Release date: 01/10/2012

OR

(ii)    SpeedNet Client Version 3.2 Beta (Released to Sorting / IC Hubs for Bulk Delivery)

OR

(iii)   SpeedNet Client Version 4.0 (Released for testing of SP-COD and BRSP)

OR

(iv)   SpeedNet Client Version 4.1 (Release date 31/10/2013)

OR

(v)    SpeedNet Client Version 4.1.1 (Release date 02/12/2013)

c)   For Post Offices: Meghdoot 7.9.2 (for SP-COD operations)

5)     Other Requirements:

a)            .Net Framework 2.0 or higher.

b)  Windows Installer 3.1 or higher.

 

 For Fresh Installation:

a)      Download the SpeedOne Installer.exe and copy it to C Drive on your system.

b)      Run the SpeedOne Installer.exe with administrative rights.

c)       The process at (b) needs to be repeated for installation of SpeedNet Server / SpeedNet Client / SpeedNet Communication by selecting respective options.

Note:
i)        Installation from C Drive is required to avoid deep directory path errors.

ii)       Remove the installation files from the previous installation, if any, from Windows directory to avoid ‘insert disc x’ errors.

iii)     Ignore the errors related to MSDART.dll, MSJRO.dll and MSADOX.dll noticed during installation process.

 Instruction for SpeedNet Communication installation:

 a)      Ensure that SpeedNet is not in use in any system at the time of upgradation.

b)      Copy the contents of Message, RXD and TXD folders available under existing EMSClient folder to any other location.

c)       Uninstall the existing SpeedNet Communication module using options available under Control Panel à Add Remove Programs option.

d)      Install the new SpeedNet Communication module.

Note:

i)      If .Net 2.0 Framework is not available, stop here, install .Net 2.0 Framework and then proceed with step (d).

ii)    Default installation path is C:\Program Files\EMSClient

iii)   Do not forget to update the SpeedNet Communication path in SpeedNet client under Supervisor à Master à Environment à Folder Paths. 

e)      Run the SpeedNet Communication and complete the configuration.

f)       Copy the contents of Message, RXD and TXD folders of older EMSClient folder to the respective folders of new EMSClient folder for transmission / processing.

For Upgradation:

a)      Download the SpeedOne Updater.exe and copy it to SpeedNet folder on client system.

b)      Run the SpeedOne Updater.exe with administrative rights.

c)       Fresh installation of SpeedNet Communication is mandatory. Procedure for installation of SpeedNet Communication is detailed under section “For Fresh Installation”.

d)      Run SpeedNet Communication after upgradation in any one client system so that the version messages are created immediately. This helps in avoiding the process for DB upgradation each time when ever upgradation of SpeedNet is done in other client machines.

Note:

a)    Take full backup of existing databases (i.e., POSPCC and POSPCCBACKUP) before attempting upgradation.

b)   Ensure that SpeedNet is not in use in any system at the time of upgradation.

c)    Check the contents of Log files available in the DB Scripts à Log folder for details of upgradation issues and errors, if any.

d)        Script files i.e., EXL files available in the ‘DB scripts’ folder under SpeedNet folder can be executed (using Meghdoot Script Tool) to re-perform upgrdation process as per the advice of CEPT.


a)      Check the version of SpeedNet Client – It should be 4.2

b)      Check the log files of SpeedNet Communication – The naming convention for log files is SC_ProcessLog<ddmmyy>.txt and SC_ErrorLog<ddmmyy>.txt

c)       Check the status of SpeedNet MIS for updation of version status of your office

d)      Sorting Hubs / IC Hubs: Check Bulk Delivery menu is shown. If not shown, check the Office Code configured for your office under Supervisor à Master à Environment à My Office Details. If Office Code is wrongly configured, please re-configure the Office Details.

e)      Offices other than Sorting Hub / IC Hub: Check Delivery menu is shown. If not shown, check the Office Code configured for your office under Supervisor à Master à Environment à My Office Details. If Office Code is wrongly configured, please re-configure the Office Details.

f)                  Check the menu options, SP COD Transfer to Meghdoot Postman and BRSP Articles (only for Post Offices) and Bulk Delivery (only for Sorting Hubs / IC Hubs) – If disabled for Operators, then enable the respective menu options using Supervisor à Master à Duty Allocation à Modify option.

g)      Check the BNPL customer, My Office Details and Folder Paths configuration for SP-COD – It should be configured as illustrated in SP-COD PPT.

h)      For SP-COD requirements, pushing & pulling of data between Meghdoot & SpeedNet Servers is done using Link Server concept (Remote connections). 

Procedure to enable remote connections on the instance of SQL Server that you want to connect to from a remote computer is explained below:

1.  Turn on the SQL Server Browser service.

2.  Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.

3.  To enable remote connections on the instance of SQL Server 2005 and to turn on the SQL Server Browser service, use the SQL Server 2005 Surface Area Configuration tool.

Note: 

1)  The Surface Area Configuration tool is installed when you install SQL Server 2005.

      2)  For SQL Server 2000, remote connections are enabled by default. For SQL Server 2008, the options are similar to SQL Server 2005. 

You can view further information at http://support.microsoft.com/kb/914277. 

i)                   Download the Office Data of your Circle from SPC site and update this data using SpeedNet Communication --> Tools --> Update Office Data option --> browse and select the downloaded file to update the office data.

 
Bugs fixed in SpeedNet 4.0 Release dated 12.09.2013: 


Fixed the bug causing the error based on the feedback received from field units regarding errors during modifying remarks under the option Operator à Delivery à Remarks From Other Offices à Speed Post Articles à View/Modify. 


Missing of remarks for articles, which were received missent at POs and returned to Sorting / IC Hub, was resulting in low KPI scores for few POs in Delivery PO Performance Report and same was reported to CEPT. Hence, despatch of such articles without being scanned under the option, Operator à Delivery à Dispatch à Missent Articles is restricted. 


Based on the feedback received from field units regarding Deadlock in SQL Server while closing of SP Bags, the bug causing the error is fixed. 


Based on the feedback received from field units regarding error while taking returns for missent / redirected articles which were received back at same office, the bug causing the error is fixed. 


Virtual Scanning logic is revised to address the issues relating to virtual scanning. 


Errors reported during opening of Transit bags and bundles have been fixed. 


Errors reported during modification of bags opened (including transit bags) under Supervisor à Modifications à Alter Bags Opened à Add / Modify an Article option have been fixed. 


Various errors / issues reported during fetching of data from Point of Sale Counter database have been addressed. 


Based on the feedback received from field units regarding non-tallying of abstracts, we have analysed the issue and found that, transfer of articles from Operator to supervisor and vice-versa are not being done in SpeedNet as per the prescribed procedure resulting in discrepancies related to opening and closing balances in abstracts. Hence, we have modified the logic to get opening / closing balances of all active users on Supervisor’s Shift End to tally the abstracts. 

Important Note: 

Upon upgradation to SpeedNet Version 4.0, Supervisor should initialise the Opening Balance of each User under the option, Tools à Bulk Transfer à Initialise OB.

In case, if Opening Balance of any user is not initialised, then Set Article Abstract / Office Article Abstract / Bag Abstract may result in incorrect figures. 


Discrepancy report is revised to show details of articles received but not disposed, articles collected but not disposed etc., 


Due to non-handling of Office Code for Offices like MBC, BNPL etc., configuration of Mail List option was having errors at these offices. This has now been fixed. 


Logic for flushing data is revised to speed up the process of data flushing. 


Active status for offices has been implemented to exclude old offices data while showing the office name in drop down list of Receipt of Bag option, Opening of Bags option, Closing of SP Bags option etc., 


Billing logic for Post Paid / Advance customers has been modified to exclude discount on tax values. 


Period of retention of delivery data has been extended from 35 days to 45 days so as to enable generation of Speed Post MIS – Delivery Performance report upto 15 days after the completion of month.


Please provide your feedback or report on errors by raising tickets on HDMS at http://cept.gov.in/ or sending mail to support@ceptmysore.net. 

Subject for your feedback or report on errors in mail should be:

SpeedNet Version 4.2 – Feedback / Error report