FW: UNC names??

How do you make use of UNC names (Windows NT) for Directory and FileNames.
in the following code sample:
sFileName : string = '${forte_root}\\tmp\\lmtest.txt';
sdirName : string = '\\\\HUNT051\\Squirl';
sTestLine : string = 'Howdy Ho Lawrence';
oFile : File = new();
oFile.SetLocalName(Name = sFileName);
oTargetDir : DirectoryFile = new();
//oTargetDir.SetLocalName(name = sdirName);
oTargetDir.SetPortableName(name = sdirName, noParse = TRUE);
oFile.Open(accessMode = SP_AM_WRITE , isBinary = FALSE);
oFile.WriteText(Source = sTestLine, length = 0);
oFile.Close();
oFIle.CopyFile(Target = oTargetDir);
the following error occurs:
ImageCollectorWin_cl0: SYSTEM ERROR: System Error: Permission denied,
opening '\\HUNT051\Squirl' with mode 'wb'
Class: qqos_FileResourceException
Error #: [101, 184]
Detected at: qqos_File::Open at 4
Last TOOL statement: method CollectorController.DoFileTest, line 15
This is despite the share and world full access permission set up on that
directory.
Thanks..
Lawrence J. McLean Ph: +61 2 9239 4971 (at LawPoint Pty. Ltd.)
Oryx Technology Pty Ltd Fax: +61 2 9239 4900
Company E-mail: lawrence.mcleanoryx.com.au
Personal E-mail: mcleanlozemail.com.au
****************************************************************************

Similar Messages

RE: (forte-users) FW: UNC names??

It appears you are attempting to call the CopyFile() method to copy a file
to a directory file. You should be copying a file to another file. Notice
your error message implies that you are trying to open the
'\\HUNT051\Squirl' directory in 'wb' mode.
Hope it helps,
Hans Ringsak
Andersen Windows, Inc.
phone: 651/439-5150 x2801
e-mail: HringsakAndersenCorp.com
-----Original Message-----
From: Lawrence McLean [mailto:lawrence.mcleanlawpoint.com.au]
Sent: Wednesday, January 12, 2000 5:57 PM
To: kamranaminyahoo.com
Subject: (forte-users) FW: UNC names??
How do you make use of UNC names (Windows NT) for Directory and FileNames.
in the following code sample:
sFileName : string = '${forte_root}\\tmp\\lmtest.txt';
sdirName : string = '\\\\HUNT051\\Squirl';
sTestLine : string = 'Howdy Ho Lawrence';
oFile : File = new();
oFile.SetLocalName(Name = sFileName);
oTargetDir : DirectoryFile = new();
//oTargetDir.SetLocalName(name = sdirName);
oTargetDir.SetPortableName(name = sdirName, noParse = TRUE);
oFile.Open(accessMode = SP_AM_WRITE , isBinary = FALSE);
oFile.WriteText(Source = sTestLine, length = 0);
oFile.Close();
oFIle.CopyFile(Target = oTargetDir);
the following error occurs:
ImageCollectorWin_cl0: SYSTEM ERROR: System Error: Permission denied,
opening '\\HUNT051\Squirl' with mode 'wb'
Class: qqos_FileResourceException
Error #: [101, 184]
Detected at: qqos_File::Open at 4
Last TOOL statement: method CollectorController.DoFileTest, line 15
This is despite the share and world full access permission set up on that
directory.
Thanks..
Lawrence J. McLean Ph: +61 2 9239 4971 (at LawPoint Pty. Ltd.)
Oryx Technology Pty Ltd Fax: +61 2 9239 4900
Company E-mail: lawrence.mcleanoryx.com.au
Personal E-mail: mcleanlozemail.com.au
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com

Thanks Ringsak,
I eventually figured out the solution.
It appears to be an idiosyncrasy of Forte. if you specify the directory name
as say:
oTargetDir.SetLocalName(name = 'C:\\Squirl');
That works fine,
However, to make a UNC specification to work, the trailing slash must be
included, for example:
oTargetDir.SetLocalName(name = '\\\\HUNT051\\Squirl\\'); // this works
oTargetDir.SetLocalName(name = '\\\\\HUNT051\\Squirl'); // this does not
work
Thanks,
Lawrence
-----Original Message-----
From: Ringsak, Hans (ATI) [mailto:HRingsakAndersenCorp.com]
Sent: Friday, January 14, 2000 4:19 AM
To: kamranaminyahoo.com
Subject: RE: (forte-users) FW: UNC names??
It appears you are attempting to call the CopyFile() method to copy a file
to a directory file. You should be copying a file to another
file. Notice
your error message implies that you are trying to open the
'\\HUNT051\Squirl' directory in 'wb' mode.
Hope it helps,
Hans Ringsak
Andersen Windows, Inc.
phone: 651/439-5150 x2801
e-mail: HringsakAndersenCorp.com
-----Original Message-----
From: Lawrence McLean [mailto:lawrence.mcleanlawpoint.com.au]
Sent: Wednesday, January 12, 2000 5:57 PM
To: kamranaminyahoo.com
Subject: (forte-users) FW: UNC names??
How do you make use of UNC names (Windows NT) for Directory and FileNames.
in the following code sample:
sFileName : string = '${forte_root}\\tmp\\lmtest.txt';
sdirName : string = '\\\\HUNT051\\Squirl';
sTestLine : string = 'Howdy Ho Lawrence';
oFile : File = new();
oFile.SetLocalName(Name = sFileName);
oTargetDir : DirectoryFile = new();
//oTargetDir.SetLocalName(name = sdirName);
oTargetDir.SetPortableName(name = sdirName, noParse = TRUE);
oFile.Open(accessMode = SP_AM_WRITE , isBinary = FALSE);
oFile.WriteText(Source = sTestLine, length = 0);
oFile.Close();
oFIle.CopyFile(Target = oTargetDir);
the following error occurs:
ImageCollectorWin_cl0: SYSTEM ERROR: System Error: Permission denied,
opening '\\HUNT051\Squirl' with mode 'wb'
Class: qqos_FileResourceException
Error #: [101, 184]
Detected at: qqos_File::Open at 4
Last TOOL statement: method CollectorController.DoFileTest, line 15
This is despite the share and world full access permission set up on that
directory.
Thanks..
Lawrence J. McLean Ph: +61 2 9239 4971 (at LawPoint
Pty. Ltd.)
Oryx Technology Pty Ltd Fax: +61 2 9239 4900
Company E-mail: lawrence.mcleanoryx.com.au
Personal E-mail: mcleanlozemail.com.au
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.sageit.com

Can't add own application to RemoteApps - "You must specify a file from the RD Session Host server SERVERNAME by using the UNC path....

Hi, there
I'm not really pro- at RDS in server 2012 (r1), but I have a problem and don't find anything suitable on internet:
I'm trying to publish one of my own, unlisted programs to rdweb, but it keeps saying "You must specify a file from the RD Session Host server SERVERNAME by using the UNC path...."
1) I provided the path in the unc name - when I click "Add.." then i browse the the .exe file via network share, not via local path. So that should be OK
2) Firewall is turned off and eventhough the exeptions are enabled, both of then, checked
What else should I do to make this work?

Okej, I found the sollution:
You have to specify the path like \\hostname\drive_letter$\path-to-the-program.
I was doing wrong because i wrote it like \\hostname\ShareName\path-to-the-program.
I was misleded because the wizard wants me to find the program by clicking, and not by entring the path manualy.

Problem entering the Host Printer name in SPAD...

Hi,
I have problem configuring the printer in SPAD. In the access method, I am trying to add the TCP/IP address of the network printer instead of the printer UNC name. Is this the problem ?
If yes then how do I get the UNS name of the printer attached to Windows NT system ?
Regards,
Rajesh.

Hi Rajesh,
Using IP address for the printer should not be an issue. But still UNC name is preffered option. You can get this information for the administrators of the print server you are using.
Please award points if you found the answers useful.
Regards.
Ruchit.

The parameter is incorrect Error when browsing by name

I have a domain setup, When i try to browse my "servername - share" i recieve the following error
"servername - share" is not accessible. you might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
the parameter is incorrect.
if i browse "ip address - share" i get in no problem
also if i browse by fully qualified domain name the the directories are empty

Hi,
Please try to use UNC name to access the folder to check the result.
Also, try to use another account for test or using another client to access the share folder.
In addition, here is a thread for your reference:
Parameter incorrect error after browsing network drives.
http://social.technet.microsoft.com/forums/en-us/w7itpronetworking/thread/192F6F59-D4AF-4FD1-A411-74A3A4E9A022
Hope this helps
Vincent Wang
TechNet Community Support

HELP: SP01: Printer Name is Invalid

Hello SAP Friends/Gurus,
I am getting "The printer name is invalid" error message in SP01, when trying to print in SAP:
Windows/NT error 1801 [
<my machine name>\<my printer name>]: "The printer name is invalid."
The thing is, my machine and printer name are both correct. I even tried changing the settings of my printer (from its hostname to its IP address) in SPAD. My printer is directly connected to my computer.
Also, I could not print using LOCL.
Any suggestions on how to resolve this? Thank you very much in advance!
Best Regards,
Albert

Hai,
Are you using 'C' as your access method, check that.
This message indicates that the printer name is invalid or otherwise incorrect. Click on Start > Run, and enter the same UNC to see if the printer can be accessed manually. If attempting to set the printer as default, the printer name and the share name must match exactly same (case sensitive also).
Enter the UNC name of the printer (name and network path) as it is defined in the Microsoft Windows Print Manager.
For example:
P09330\P330
http://help.sap.com/SAPHELP_NW70/helpdata/EN/26/ceea3b31aac554e10000000a114084/frameset.htm
Regards,
Yoganand.V

Can I use WNT UNC for file url crawling

If I set up a Mapped Drive on Windows NT (e.g., E), I can specify and crawl a file URL that has been entered
like file:///E:/folder. The problem is that the Mapped Drive is only available while I am logged onto the PC.
What I need to be able to do is specify a valid UNC in the File URL like
file:///hostname/folder/subfolder
I tried the above format, but got an error.
Does anyone know if and how to specify File URLs using UNC name ?

File URL crawling does not support UNC in current version.

Addintional directories and UNC

I want to add an additional directory that resides on another server. The admin console seems to accept it, but any access results in a "forbidden" error. Nothing is logged. Although the documentation says nothing about UNC paths, the console at least must have some level of support for it since an invalid UNC gives an error message while a correct one does not. Anyone knows anything about this?

I have now tested using a UNC name from withing a JSP page to open a file and read from it, and it works. The file I accessed is the exact same file that the NameTrans/pfx2dir directive in server1-obj.conf is supposed to evaluate to. Accessing the file through the SunONE http server failes though. I searched the entire AS7 collection for the word UNC. No matches found. If UNC names aren't supported, is there another way to link an additional directory to a shared directory on another NT server?

Getting file from local network computer

Hi! I have a problem to get the file form local network. I have tried following ways to do it:
new File ("file://10.150.11.214/pics/bilde.JPG");
new File ("smb://10.150.11.214/pics/bilde.JPG");
new File ("http://10.150.11.214/pics/bilde.JPG");There is always error:
java.io.FileNotFoundException: file://10.150.11.214/pics/bilde.JPG
(The filename, directory name, or volume label syntax is incorrect)On the local computer IP is 10.150.11.214 and shared folder "pics"
Can U give me some solution!
tnx! ;)

Manivel wrote:
+@kajbj+
Why? The problem is already solved.
 
Yes correct, but see OPs previous post.
+PeterisR wrote
I had tried as U sad, Manivel! but there were problems .. tnx, anyway!+Ok. I can understand that you want to know why / how it failed, but using URI/URL is in this case not the best way. Using the normal File class and UNC name is far more common.
Kaj

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Multiple Machine Render question

Alright, so I just realized that After Effects (I'm running CS3) can utilize multiple machine renderings. At first, I thought this would be great since my typical renders are anywhere from 45 minutes to 2 hours. But, after much playing around, I realized that it only works for sequences.. which isn't much help because I export the majority of my work as DV Streams or MOV files! Is there any way I can get it to do formats other than image sequences or am I SOL?
I also considered buying a few moderate-end machines and putting together a small render farm in case I couldn't, but I wouldn't know where the best place is to start with something like that (I'd imagine determine what software works, but I can't find much info on that, really).

for PC's only =====
i wrote my own dos scripts to setup network rendering (remotely start after effects engines, copy projects to a watchfolder, and setup RenderControlFiles, copy and install fonts, etc ... took me a while to write and set up and is really the property of the company I work for), but the basics are below and from my in-house help file. Works better for us than collecting footage, basically, just substitute local drive volume names with UNC names, save the project, submit to the watchfolder, in its own directory, and add an RCF text file (try collecting footage, an RCF file will be generated so you can see whats in it). The thing that took me longest to debug was to install required fonts remotely ... any way read the basics
THE FOUR BASIC REQUIREMENTS
The basic requirements for any software that can network render, are that
(1)
all participating computers are able to access the original source footage,
(2)
any required fonts are loaded and active on the participating renderers,
(3)
any plugins and codecs used are also installed and available, and
(4)
all rendered frames, ie, output are send to a common storage area; single frames sequences are the best output format, a single streamed format, like an AVI, MPEG, or Quicktime Movie cannot be created by more than one computer at one time. However if your render queue has multiple single file streams queued, multiple render slaves can render the multiple queued streams, with one slave rendering one of the streams at a time two or more render slaves cannot render the same stream at the same time.
SETTING UP YOUR PROJECT TO NETWORK RENDER
Source Footage Paths
The first problem in the below example is that all the source footage is referenced using local paths. The default network rendering method Adobe use is really best suited to archiving, wherein the footage is collected from the source computer and copied to a common server in a hierarchial tree structure. In this example the source footage is comparatively short, but still over 900mb long, so there is a time issue involved, a network traffic issue, a storage issue at the server end, a server management issue, and if the network render fails, or needs to be redone, this step will need to be repeated or the process hacked by an appropriately skilled person.
To network render, all source imagery should use a file path that can be seen by other computers on a network. The best method is to use UNC (universal naming convention) paths, ie \\computername\sharedvolume\foldername\foldername\imagename.
In the above example a badly pathed file N:\TV1 Promos\sas\sas1.aif could be made legal by re-pathing to \\regan\zone2\TV1 Promos\sas\sas1.aif assuming that zone2 is an explicitly shared volume.
TIP: you can create as many share points as you want. You could, for example create an additional share point N:regan\one2\TV1 Promos\sas and call it SAS so it appears as the share \\regan\SAS. Just right-hand click on the folder you want to share, select SHARING from the menu, create the new share and give it a meaningful name; on XP systems, you also need to specify read/write access permissions.
You can create a shortcut to this or any other share, leave it on your desktop, and that will save you time navigating to that point or typing out \ \ r e g a n \ s a s
Alternatively, you can highlight a network path in explorer, copy that text, and keep pasting it when subsequently specifying paths.
There are not limitations on how many share points you can create.
An further alternative method would be to use the administrative share path, \\regan\N$\TV1 Promos\sas\sas1.aif. Here the drive letter N: is replaced by \\regan\N$. This method is particularly useful where the volumes are not explicitly shared.
One other method is to map shared volumes or folders to a drive letter, but for this to work, the drive mapping must be consistant across all participating renderers, so you would have to run around these computers mapping network shares to drives on a per job basis as required, so it is not at really very practical.
After Effects 6.5 introduced a smarter way if the project is opened on another computer on the network, it will attempt to replace the locally specified footage paths, with network paths. Mostly it works okay, sometimes it doesnt. Footage that is sourced from mapped network drives, for example where W: drive refers to \\Gfxserver2\graphics2, will have problems.
The best way is to use the UNC paths from the begining of the projects construction, then there is never an issue, and the project will always be portable, but if you forget or cant be bothered, or think that using network rather than local paths is slowing you down, ...
1) save your project,
2) open your project on another machine
3) reload one of the missing footage files ... the rest should fill themselves in, if they dont they are probably on another drive
4) check the output is network pathed
5) save the project, and submit that version to the render farm
Ultimately, for this project to network render successfully, the source footage needs to be completely specified in a manner where it is accessable by any machine on the network, so use must be made of
\\computername\VolumeLetterDollarSign\foldername\foldername\imagename, or
\\computername\sharedvolume\foldername\foldername\imagename, or
\\computername\sharedfolder\imagename methods.
Output Footage Paths and Render Settings
Once the source files have been amended to include a full network pathname, the parameters for the render can be set.
STEP ONE
In the Render Queue window, firstly choose a single frame Output Module, such as TARGA or JPEG; a single file streamed format, like an AVI, MPEG, or Quicktime Movie CAN NOT be created by more than one computer at one time. However if your render queue has multiple single file streams queued, multiple render slaves can render the multiple queued streams, with one slave rendering one of the streams at a time two or more render slaves cannot render the same stream at the same time.
STEP TWO
In the Render Settings, make sure you turn off storage overflow and turn on skip existing frames so that once any frames that have been network rendered, those frames will not be rendered again by another machine.
STEP THREE
The destination for the outputted animation should include the full network pathname, so that all the outputted files end a up in the same place.
Warning: If local paths are inadvertently used here the rendered files could be scattered over any local hard drive of the machines that will be rendering the animation, and each rendering machine would not be able to determine which frames had been rendered by other machines, so each machine could end up rendering the entire sequence itself, it the drive letter exists on that rendering machine.
Again it doesnt really matter which of the network naming methods is employed; either
\\computername\VolumeLetterDollarSign\foldername\foldername\imagename, or
\\computername\sharedvolume\foldername\foldername\imagename, or
\\computername\sharedfolder\imagename will work.
STEP FOUR
The project with its network pathed source and output files specified, and render queue setup would then be saved.

Is it possible to search the client for a file in WebDynpro?

Hi,
I need to check inside a WebDynpro application wether a
file exists on a client or not, befor showing or listing it.
I have a UNC-Name for the location (e.g.
servername\dirname\filename.extension).
Another task would be to browse this directory for all other existing files and dirs and list them.
Is this at all possible with WebDynpro?
Or would this only be possible by using the filesystem of
the applicationserver (e.g. mount the dir on the filesys)?
Is it possible to launch a client-located script (like VB-Script or such) in WebDynpro?
(e.g. to search the dir, create a text-file and read this text-file).
Or are these concepts totally against the security-policies
of web-based applications?
Thanks in advance.
Alf

Hi Alfred,
generally web applications run in a sandbox on the client.
That means that they have no access to the file system.
To get access you need to install a certificate on the client:
You create a key with the Java-Tool "Keytool" and sign the application (or the applet) with the Java-Tool "Jarsigner".
That generates a *.cert file wich you now have to export from the parent system and import onto the client (with Keytool).
You will find many detilled instructions for this procedure in the internet.
Unfortunately I don`t know how it works with Web Dynpro.
Karsten

How do you configure the server in this situation?????????????

Hi,
We have Oracle 10.2 and Windows 2003.
We have Oracle on Cluster (with Windows software).
When the System are without cluster all its OK!!!!!!
We have 2 Resources Cluster Group: Oracle and Applications.
We have Oracle in Oracle cluster group.
We have W Drive and a ftp program in Application cluster group.
We have C drive in both nodes. We have installed Oracle in both nodes but we have W drive only associate to the Active Node because is a Cluster resource (Application cluster group).
All days we receive text files by ftp and we put it on W Drive. This text files are readen with external tables in Oracle.
We have a problem when oracle fails and it goes to the another node (for ex. node2) because the external tables fail because the files are on Node1 on W Drive. If we move manually Applications cluster resource to Node2 then all it is OK.
We think to put UNC pathes instead of W but its not possible (Metalink: Note:290703.1)
How do you configure the server in this situation?????????????
Thanks!

We run a similar configurations and i doubt you have a chance other then reconfigure your setup. The way we do it is to have an ftp client in our database group and periodically transfer the files a second time (not elegant but it's working).
If that's not an option you might be able to use unc names in your ftp server and set the ftp root to a directory hosted on a disk which is part of the database group.
Or move to unix (that's what we do now). Than you don't have to bounce your server once in a month to apply security patches...

Excel 2010 cannot open ~xlsx file from WD ShareSpace

Excel fails to open an ~xlsx file from the Western Digital NAS. It shows downloading .... than fails cannot open file.
The file was previously fine and if it is copied the copy opens easily. If the copy is renamed I can use Excel's recent files option to open it. The old file cannot be opened even if renamed.
I can typically use the file for a day or so, then it becomes unusable. It cannot be opened from another Windows 7 machine either but again a copy is accessible.
The files are small typically 100Kb, password protected
Windows and Office are up to date on both machines
The problem is becoming more frequent with no apparent cause
I have tried opening from explorer, the recently used files list in Excel, and file ... open
I have tried using mapped drive, UNC name, IP address
The network location is recorded as trusted
Although there is the potential to share the file it has not been opened by other users in between working and entering the state where it cannot be used.
When a file is unusable in Excel right clicking in explorer takes a long time to offer the normal context menu. However if the file is selected then copy/paste is quick and unaffected.
Please can anyone help me fix this annoying issue.

Hi,
According to your description, I have some questions.
Would you share us the whole error message when opening the special Excel file?
Did the copy file work well in the NAS?
Did you move the special Excel file to another NAS folder to test?
Did the special Excel file works well in the local disk (Download it)?
Then, I suppose that the file may be used by other program\handle\process in the background during opening process. Please try to use the tool named
Handle (It is a utility that displays information about open handles for any process in the system. You can use it to see the programs that have a file open, or to see the
object types and names of all the handles of a program.) to check.
Steps:
Copy handle.exe to C:\Windows\system32 folder.
Run cmd.exe as administrator
Type handle -a C: /Test/test in command prompt, then it will list all handles and processes accessing this folder.
4. It shows that cmd.exe is accessing c:\Test\test. Then, we can use
handle –c command to close the handles, along with
the handle ID, and the process ID, and the "-y" switch to confirm the delete.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Quickly reconnecting large numbers of photos in PSE 6 and 7

[This is a significant revision of my message posted here on 2/8/2008 and in the Photoshop Elements 6.0 FAQ forum on 2/9/2008. It is split across two messages.]
Part I of II
When you move photos from one location to another using Windows Explorer or some other tool outside of the Organizer, PSE reports those files as missing, and a question mark appears on the thumbnails in the Organizer. The File > Reconnect command can reconnect those files with their new location, but it can be very slow and sometimes only connects a few files at a time.
Its always best to move files and folders using the Organizer, avoiding the need to reconnect. But if youve already moved those files, here are some ways of coping in PSE 6 and 7:
1. Move the files back to their original location using Windows Explorer. Then use the Organizers Display > Folder Location view or the File > Move command to move the files to the desired new location. In the left-hand folder pane of Folder Location view, you can drag and drop folders, just like in Windows Explorer (this isnt documented in the Help).
Since the File > Move command moves files to a single destination folder, its not that useful for working with more than one folder. The PSE 6 Move command also has a serious bug if you move a file to a folder that already has a file of the same name, the destination file gets permanently deleted. (Thats fixed in PSE 7.)
2. Reconnect an entire folder all at once. If you cant or dont want to use the first method, you can use File > Reconnect > All Missing to reconnect more than one file at a time.
Its not immediately obvious, but the Reconnect > All Missing window can reconnect an entire folder of files all at once. On the left-hand side, under Files Missing from Catalog, click Select All. On the right side, under Locate the Missing Files, browse to the folder containing the files. A thumbnail of one of the files should be displayed. Click Reconnect, and all the files in the folder will be reconnected. If there are files in other folders remaining to be connected, theyll still be displayed on the left, and you can repeat the process.
3. Reconnect an entire folder tree all at once. If youve moved an entire tree of folders and theyre now disconnected, you can persuade PSE to reconnect them all quickly.
a. In Edit > Preferences > Files, select the option Automatically Search For And Reconnect Missing Files.
b. Do File > Reconnect > Missing File to reconnect one file manually.
c. Do File > Reconnect > All Missing. PSE will start searching near the folder containing the missing file you reconnected in step b, and it will usually find all the missing files within a couple of minutes of searching.
d. If step c doesnt find all the missing files, or youre impatient, you can explicitly tell PSE where to search:
]i. Do Help > System Info and write down the folder location of your catalog.
]ii. Exit PSE.
]iii. Use Windows Explorer to navigate to the catalog folder.
]iv. Open the file rmf.3.cache in Notepad. This file was created in step b above. It contains the most recent folders in which you reconnected files (rmf = reconnected media folders), and the Reconnect command always searches these folders first before scanning the rest of your drives.
]v. Delete all of the contents of the file and add a single line containing the full path of root of the folder tree containing your photos. For example, if you moved the folder tree to E:\data\photos, add that as a single line to the file.
]vi. Save the file.
]vii. Restart PSE and do File > Reconnect All Missing again. It should first search the folder tree you provided in step v.

Part II of II 4. Reconnect folders residing on a network drive. If youve moved folders that originally resided on one network drive to another network drive, the Organizer will treat them as offline rather than missing, and it will show a red circle with a vertical line in the corner of the thumbnails. An offline file is one that might show up later on, such as when you reconnect your laptop to the network containing your file server or you insert a DVD containing your archived photos. Since the moved files are offline, the PSE 6 Reconnect All Missing command wont do anything but tell you there are no files to reconnect. You can force PSE to reconnect many offline files at once: a. Select all the photos that are offline. b. Do File > Write Keyword Tag and Properties Info. c. In the Find Offline Volumes window that pops up, select Reconnect and click OK. Unfortunately, method 3 doesnt appear to work with offline files on a network drive. If you have a large number of individual folders and dont have the patience to reconnect each folder in turn, you can either use method 1 (restore the files to their original location) or recreate the original UNC name for the network drive (e.g. \\mycomputer\share). (You could also try editing the catalog file using the tool sqlite3 search these forums for how to do it. But thats sketchy at best.) ------------------------------------ If you reconnect a file and get the message <old file> was not connected to <new file> or The file already exists in the catalog, then youve stumbled over a PSE bug for which there are workarounds. See this thread: <a href="/webx?14@@.59b66777/5">John Rolfe Ellis, "Cannot Reconnect; File already exists" #6, 17 Sep 2008 2:49 pm</a> ------------------------------------ I havent tested any this in PSE 5, so I cant say how much works the same way.

FW: UNC names??

Similar Messages

Maybe you are looking for