grmtech

Digital Marketing Servicess

Grow Your Client Base With Data-Driven and   
Strategies

GET MY FREE PROPOSAL 

Let’s Grow Digitally

With Our Trusted Digital Marketing Service

Read More

Great Media Technologies Pvt Ltd (Grmtech) is a Kolkata-based IT and ITeS company founded in May 2003.

Grmtech develops and maintains its projects in the USA with its associate companies. These projects are from the finance and legal industry in the USA. Grmtech has 2 offices in Kolkata, over 15 medical clinics, and 2 legal offices in California.

We work with Stanford Hospital mental health doctors and psychologists across the USA.

Grmtech does all back office work for Savantcare doctors, like managing patients' appointments, providing doctors assistance on the phone, chat, and email. We also work for OVLG to provide the best legal services in the US. We have a qualified FC team and a CRA team who offer free budget counseling sessions to clients and negotiate with their creditors for settlement.

Digital Marketing Services

 

Web Development
  • Website development
  • UI/UX design
  • Website maintenance

 

Social Media Marketing
  • Content sharing and engagement. Influencer marketing.
  • Social listening and reputation management.
  • Social media contests and giveaways.

 

Pay per Click Service
  • Google Ads.
  • Bing Ads.
  • Display advertising.
  • Social media advertising (e.g., Facebook Ads).

 

Web Analytics
  • Analyzing website and campaign performance
  • A/B testing and conversion rate optimization
  • User behavior analysis

 

Mobile Marketing
  • Mobile-optimized websites and apps
  • SMS marketing
  • In-app advertising

 

Marketing Automation:
  • Email automation
  • Lead nurturing
  • Workflow and campaign automation
Steps for fresh Windows XP installation on a Virtual machines. Preparation LSI storage controller drivers are not available on the Windows XP installation CD, so complete the following preparation before installation: 1. Download the LSI 53C1030 drivers from the LSI Web site. 2. Using MagicISO or other third-party solutions, create a .flp image containing the LSI Logic drivers. 3. SCP the floppy image to the virtual machine’s ESX host. If you are using VirtualCenter 2.5, you can use the VIC to upload the file to the desired datastore. 4. Have a Windows XP CD or ISO image that is accessible form the virtual machine. Pre-installation Virtual Machine Modifications Make the following modifications to the virtual machine hardware profile before starting the Windows XP installation: 1 Using the Virtual Infrastructure Client (VIC), connect to VirtualCenter. 2 Locate the virtual machine that was initially created. 3 Edit the following hardware settings: a Ensure there is a floppy drive present. b Ensure the floppy drive is configured to connect at Power On. c If using a floppy image, ensure the Device Type is set to use a floppy image and is pointing to the LSI Driver image. d Ensure the CD/DVD drive is present and configured to connect at power on. e Ensue the CD/DVD Device Type is configured to point at the Windows XP CD or ISO image. Installation Once you complete the pre-installation preparation and modifications, you can install Windows XP: 1 From the Virtual Infrastructure client, connect to VirtualCenter. 2 Power on the virtual machine created earlier. 3 Use the console to view the boot process and to send input to the virtual machine. 4 As the Windows Setup process begins, press F6 to add an additional SCSI driver. This lets you specify the LSI Logic driver on the floppy image. The Windows setup process copies all the necessary files to the virtual disk. Complete the setup just as you would for any normal Windows XP installation. Because this image will be used as a template, however, it is a good idea to make the configuration as generic as possible. For an instance of customization, see “Creating a Guest Customization” on page 4). After completing the Windows setup, perform the following tasks before you finalize the image. Some of these steps will vary from organization to organization, depending on your Windows imaging standards; some are optional and noted as such. Many can be managed using a group policy (see “Common GPOs for Managing Virtual Desktops” on page 5).