FLEXlm license finder issue

During customization of 3ds Max 2009 Software Package for Network deployment described on AutoDesk web site (http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=14195309&linkID=9241177), Network License Server has been configured:

But after the installation when 3ds Max has been started, from some reason the value for Network License Server previously configured in Network deployment package is not accepted, FLEXlm license finder pop-up and ask for License File or License Server.

Solution for this can be adding System Environment variable ADSKFLEX_LICENSE_FILE with the value of @SERVERNAME and deploying on the workstations using GPO Preferences.

@SERVERNAME - is the name of your Network License server

Deploying 3ds Max 2009 using SCCM 2007 R2

Creating of Customized Network deployment of 3ds Max is described on AutoDesk web site:

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=14195309&linkID=9241177

When the creation of Network Deployment is done a shortcut 3dsmax_2009.ini is created.

Click on it will allow 3ds Max to be installed in silent mode (if silent mode is specified during network deployment creation).

This shortcut points to the subfolder AdminImage which call setup.exe, use switch /I and 3Dsmax_2009.ini file created by Network deployment procedure.

setup.exe /I 3Dsmax_2009.ini

Note:
setup.exe and 3dsmax_2009.ini contains network UNC path where they are physically located.

\\server\share\3dsmax_2009\AdminImage\setup.exe /I \\server\share\3dsmax_2009\AdminImage\3dsmax_2009.ini

Using this syntax  SCCM package can be created and 3ds Max 2009 will be successfully deployed:

nvpxplugin.dlm failed to initialize

DLL C:\Autodesk\3ds Max 2009\PluIns\nvpxplugin.dlm failed to initialize.
Error code 14001 - This application has failed to start because the application configuration is incorrect.

This error message appears when Autodesk 3ds Max 2009 has been launched on Windows XP SP2 64-bit.

Solution is to reinstall the following applications:

• NVIDIA PhysX System Software

        http://www.nvidia.com/object/physx-9.10.0513-driver.html

•  NVIDIA_PhysX_Plug-in_3dsMax_x64_2.01.1222.0945.msi

        http://developer.nvidia.com/object/physx_dcc_plugins.html
        Plugin for 3ds Max is free but it requires to register to download it.

Change Virtual Memory using Group Policy Preference

To change Virtual Memory on Windows 7, the following registry key should be modified:

Value type: REG_MULTI_SZ
Value Name: PagingFiles
Value Data: c:\pagefile.sys 73725 73725

In Value Data there is a location and page file name, first 73725 is initial size, second 73725 is max size.
Registry path is:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

 

 To deploy this Registry Key you can use Group Policy Preference.

Open Group Policy Management Editor, Preferences, Right click on Registry -> New -> Registry Item. 

Enter the values from the beginning of this article:

Apply this GPO to the Computer accounts and restart the computers.

How to find MAC address remotely

On remote system which is non-windows and where we cannot use getmac command there is another way how to find MAC address remotely.

In Command Prompt use a command: nbtstat -a machinename

MAC address is at the bottom.

DPM 2010 and Hyper-V VMs restoring and merging snapshots

When we restore VMs using DPM  2010 in the Network folder except VHD file we have snapshots AVHD files.

But, the issue here us that we cannot import all these VHD and AVHD files into the Hyper-V Windows Server 2008 R2 Server because configuration XML files are missing.

Only way to import restored VM machine is to do MERGE of all snapshots with its previous Parent snapshot and to the end with the Original Parent VHD file.

This merging can be done using Edit Disk in Hyper-V Manager.

Here is the explanation for Disk merging:
http://blogs.msdn.com/b/robertvi/archive/2008/08/26/howto-recover-snapshots.aspx

SCOM 2007 R2: Enable the Heartbeat Failure monitor for clients computers

By default Heartbeat Failure monitor for clients computers is not enabled on SCOM 2007 R2.

To enable it you should override the Health Service Heartbeat Failure monitor from Health Service Watcher (Agent) Monitor and set the Generates Alert parameter to True.

You can do that if you open SCCM 2007 R2 console, go to Authoring, choose Health Service Watcher (Agent) on right pane, right click on Health Service HeartBeat Failure and choose Overrides Summary.

Select the line and click Edit:

Change the Generates Alert parameter to True and click ok.

Close the application.


This modification will allow, except from Servers, to receive Heartbeat Failure alerts from Clients computers.