Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
Cobra7 | 03 Mar 2009 | 1 comment

Adding Drivers to WinPE (Ghost boot wizard or Ghost Console) .                             

Note: In order to add drivers to the Ghost Console the Ghost Boot Wizard must be used.
  1. Start Ghost Boot Wizard.
  2. Select Windows PE and click Edit.
  3. Highlight WinPE and click Edit
  4. On the right wide will be a button named “Add new driver”, click it
  5. Browse to the .inf file and select it
  6. Name it the name of the driver (i.e. Intel e1000 Pro, Broadcom 57xx)
  7. Select Vista and XP and click Ok.
  8. The driver will now appear on the left side unchecked, check the box next to it.
  9. Click Ok, Ok.
  10. If you wish to make a new boot disk or VP, continue to do so, otherwise click Cancel to leave the program.
WiseUser | 18 Feb 2009 | 2 comments

The process of converting Wise Script made exe's back to Wise scripts (.wse) is not efficient with any utilities available in the market.

It is always advisable to keep a copy of the Wise script embedded in the exe, so that we can get back the project file at anytime even if the source file is lost.

Steps:

  1. Create your own Wise script
  2. Include the script in itself
  3. Compile the script
  4. Run the executable with "/script" as cmd parameter, you will get back the wise script in %TEMP% location.
Joel Smith | 02 Feb 2009 | 0 comments

The Symantec Zone on the Intel vPro Expert Center site has gone live!

Follow this Link for access: http://communities.intel.com/community/openportit/...

Access this site for all kinds of information concerning Intel's vPro technology and Symantec Products that use it.

Content

The following types of content are available at the site:

  1. Documents - including Technical papers and guides
  2. Discussion - Read or share in discussions concerning Symantec's integration of vPro's powerful set of functions
  3. Blog Post - For any topic concerning Symantec using vPro Technology
haim96 | 23 Dec 2008 | 0 comments

In my environment (NS 6) there are a lot of scheduled tasks running on permanent time and day but from time to time I need to temporary disable a task and then enable it again.

With NS 6 there is only one option to disable task:

By disabling the shared scheduled that the user uses (IF he uses...) but in this way all the tasks that use the same shared scheduled will be also disabled.

The other way is delete the scheduled task and then recreate it when you need it again. Not very good option when the task runs on a variety of collections and computers...

So I came up with another option that allow me to disable the task but keeps it from deletion (and the collections\computers selections).

Create new shared scheduled in:
Configuration-> notification sever settings -> shared scheduled.

Select "Add...

Sidd | 18 Dec 2008 | 0 comments

This document provides information about the Office 2007 System Group Policy settings from Administrative Template (ADM) files and Office Customization Tool OPA files.

Thanks,
Sid

Mags | 24 Nov 2008 | 7 comments

Ever had an Asset created where the Resource Type is incorrect, or have you had a physical server virtualised, but the Resource Type has remained as Computer instead of Virtual Machine?

Well here's a quick script to change the Resource Type for an individual resource

UPDATE vResource
SET ResourceTypeGuid = '2C3CB3BB-FEE9-48DF-804F-90856198B600'
WHERE vResource.Guid = '9f679247-fc68-4baf-9042-5571cb79ee64' 

In this example, a server, GUID 9f679247-fc68-4baf-9042-5571cb79ee64, has had its Resource Type changed to Virtual Machine 2C3CB3BB-FEE9-48DF-804F-90856198B600.

Common Resource types are:

Asset  B9EE0AB2-AE0E-4867-BF4C-41D4A382163B
Computer  493435F7-3B17-4C4C-B07F-C23E7AB7781F
Monitor  FE46D9CE-B71C-4DE4-B790-242A9EF1A5D3
Network Printer  8E4F62F4-948C-...

WiseUser | 21 Nov 2008 | 0 comments

Return codes are nothing but the errorlevels. The DOS command to determine the return code is IF ERRORLEVEL.

Errorlevels are not a standard feature of every command. A certain errorlevel may mean anything the programmer wanted it to. Most programmers agree that an errorlevel 0 means the command executed successfully, and an errorlevel 1 or higher usually spells trouble. But there are many exceptions to this general rule.

In Wise script the Variable used for getting the return code of an installation is %INSTALL_RESULT%

WiseUser | 14 Nov 2008 | 0 comments

Command line to apply multiple transforms:

Msiexec.exe /i {path}.msi TRANSFORMS=T1.mst;t2.mst

Value Supercedence:

If t2.mst contains any property or any update that t1 has made, the installation will take the final transforms value.

Ex: If t1.mst sets a reg value HKCU\Software\Test\Enviorment =0

And if T2.mst sets a different value to the same registry HKCU\Software\Test\Enviorment =1

then the instalaltion will take the reg value as 1.

tkight | 13 Nov 2008 | 12 comments

This applies to Deployment Console version 6.9

I know this will be dated soon because PCAnywhere is taking over for Carbon Copy, but it may still apply for PCAnywhere from the NS after that. Also someone may find it useful for something else. I couldn't find this anywhere else either.

I've been looking for a way to remote from the Deployment Console besides the standard remote control. I found CondorMan's excellent article here.

However, we don't use UltraVNC, we only use Carbon Copy at present. The problem is when you are working in the Deployment Console (or even in the NS console) it can be laborious to get to a Carbon Copy dialog screen. So I took what he said, and added the following to the remotecontroltools.ini file in the eXpress share:

[Carbon Copy]...