Skip to main content

opalis: provide a value expression on the right-hand side of the ‘/’ operator

another “interesting” discovery that i decided to post today since i ran into yet again and had forgotten why.  when using the run .net script object, there are a couple of caveats while using published data.  let’s run through these real quick.

first of all, to address the title of this post, we will review this error message:

You must provide a value expression on the right-hand side of the '/' operator.

 

running through the policy testing console, you can see the error problem expressed like this:

image
 

it turns out if you use the language type powershell, the published data type of “Date/Time” does not behave as expected.

image

image

 

instead, the script fails to execute.  so for instance, if i wanted to retrieve a variable out of a powershell script which represents a date/time, using this type in opalis causes script execution problems. presumably the “/” (slash) in “Date/Time” is what’s causing the funkiness.  instead, switch it to type string.  while we’re talking about the published data, this is a good segue to the next part.

image

did you notice that there “collection” checkbox is grayed out?  look at it again.  the documentation states:

If this item of data will be multi-valued, select Collection. When using a collection you must use the Add method to add items to the collection. If you are not using the collection you can use the assignment operator (“=”) to assign the value.

i guess this doesn’t apply to powershell scripts.  switching the language type to something else makes this checkbox available.  interesting though.  if you view the published data in the policy testing console, the collection checkbox IS available.  :|

check out the next screenshot.  it works anyway (as indicated by the <…>).  :)

 image

Comments

  1. Thank you for this post, I'm sure it saved me At Least an hour or 3.

    ReplyDelete

Post a Comment

Popular posts from this blog

using preloadpkgonsite.exe to stage compressed copies to child site distribution points

UPDATE: john marcum sent me a kind email to let me know about a problem he ran into with preloadpkgonsite.exe in the new SCCM Toolkit V2 where under certain conditions, packages will not uncompress.  if you are using the v2 toolkit, PLEASE read this blog post before proceeding.   here’s a scenario that came up on the mssms@lists.myitforum.com mailing list. when confronted with a situation of large packages and wan links, it’s generally best to get the data to the other location without going over the wire. in this case, 75gb. :/ the “how” you get the files there is really not the most important thing to worry about. once they’re there and moved to the appropriate location, preloadpkgonsite.exe is required to install the compressed source files. once done, a status message goes back to the parent server which should stop the upstream server from copying the package source files over the wan to the child site. anyway, if it’s a relatively small amount of packages, you can

How to Identify Applications Using Your Domain Controller

Problem Everyone has been through it. We've all had to retire or replace a domain controller at some point in our checkered collective experiences. While AD provides very intelligent high availability, some applications are just plain dumb. They do not observe site awareness or participate in locating a domain controller. All they want is the name or IP of one domain controller which gets hardcoded in a configuration file somewhere, deeply embedded in some file folder or setting that you are never going to find. How do you look at a DC and decide which applications might be doing it? Packet trace? Logs? Shut it down and wait for screaming? It seems very tedious and nearly impossible. Potential Solution Obviously I wouldn't even bother posting this if I hadn't run across something interesting. :) I ran across something in draftcalled Domain Controller Isolation. Since it's in draft, I don't know that it's published yet. HOWEVER, the concept is based off

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point . even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch. I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.   DETECTION status messages take a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough m