HSChronic

Didn't know they discouraged the use of Sub Collections. That doesn't make sense anyway. I don't want a mess of a bunch of main collections. If they let me create folders to put my collections in then yeah I wouldn't need subs. But so far I have my imaging collection set up like so Systems to Reimage -Mandatory Push - Image A -Mandatory Push - Image B So you are saying they would rather have me make 3 collections for all of those ugh.

Just in case anyone else is wondering how to delete an app (not a package) you have to retire the application then go into revision history and delete all revisions of the application. Once this is done the app will be deleted.

So I created an App-V application in SCCM vnext, it didn't work. I retired it, deleted the deployments and content off the DP. So now how do I remove it out of applications? I don't want it in there and I can't find a way to delete it

You can't have SSRS on a remote SQL instance (at least in beta 1), I tried a zillion times until I was blue in the face it doesn't seem to work with beta 1. If they are on the same box all you should have to do it configure SSRS then use the use stored credentials to get the reports to show up in the console.

I set my admin PW in the TS to l0c@l4dmin! but for some reason when I go into the OS it doesn't seem to set. Anyone else having an issue with this?

You shouldn't need to import computers anyway, that is what unknown computers is for.

You think that is bad make a sub collection and try finding that (you have to click on the collection and hit view sub collections, I know that an expand arrow was too much so you couldn't put on in there). The whole way of making and viewing collections in vNext is uber bad right now. Hopefully the next beta will fix that.

I have had nothing but issues with remote SQL instances and vnext beta 1, mostly WMI related. I also hope this will be fixed with newer builds. I got to the point where I had to set up a server just with vnext on it instead of using my regular mgmt server. The single contained site with branch DPs is working well though.

Ok it created it because I removed the DP role from my main server and installed it on the remote server. Since I don't have a main DP it can't distribute content to other DP shares unless there is an active DP to distribute from. Thus the reason it created the SMSPKGD$.

I have deployed both SQL and Oracle with SCCM. The SQL setup parameter is different than what I use. You don't need the /q on the end specify in the config file the UI type to use and use .\configfilename.ini. Also are these being downloaded to the client cache or run from the DP? If they are running on the DP the oracle command line looks fine to me, though you might have to specify a location that isn't an admin share for the response file. If they are downloading to the client cache try running the installs from the client cache launching from the directory that the client cache resides in using the exact same command line you have in the program. What are the server reports saying when the program fails?

ok so i set up a DP on a remote share on my d drive everything is working fine but I have a question about the shares themselves. I set up the share on server\dp$ then the package copied to that DP fine but I was still getting errors about not having a server\smspkgd$ share. So I created that share and it copied the package to that share too. So now I have 3 shares with a copy of the package. The source server\dp$ server\smspkgd$ How do these all work with each other? Is the smspkgd$ used in conjunction with IIS?

What do the SQL logs say? I have seen this a lot with SQL and SCCM. SQL fails to install and just kicks back some generic error to SCCM. The SQL logs will tell you more info on why it didn't install. As for replication not sure which logs would be your best bet but between SQL and SCCM and your reporting point it should give you some info.

It uses windows authentication so as long as you use IE it should be fine. Make sure the site is set to use Windows Authentication (which it should be). As far as IIS you need ASP.NET, ISAPI filters, and Windows Authentication from Role Services for Web Server (IIS), also make sure you have WCF installed. That should be enough to get it working.

Still giving me invalid namespace. I guess I will just use the all inclusive VHD since it has everything preconfigured. It sucks, I got everything working it seems minus this. Though I am not getting any notifications on updates, but the windowsupdate.log seems to be identifying and downloading them. I hope beta 2 comes out soon, I like the product but the betaness of it makes me want to go back to 2007 since everything is configured the same and works, yet it doesn't on vNext.

Edit: 2-Oct-10 I think I got this working. It seems that the instructions don't mention (oh wait there aren't any published yet) that you have to install this role on your database server. I kept on looking at the logs and it kept saying SSRS wasn't configured on ChronicMGMT which is my MGMT Point not my Database Server. So I said to myself hrmm lets try installing this role on the DB box, it can't hurt. So I go through the wizard and instead of the SSRS instance being blank it populated with the right SSRS instance without me putting it in there. So hopefully the component turns green when I reset the count.

what does the log say? As for another method of removing it, you can use the Windows Installer Cleanup util and a combo of manually deleting the files and reg entries.

You can also use the Windows Installer Cleanup util to take the entries out of the registry. Then just stop the service and manually delete the client. This will leave a mess so you are better off trying to uninstall it. Can you upload/paste the CCMSetup.log from that directory, that will give you and us a better idea on why the client isn't installing correctly or uninstalling in this case. It sounds like your client is in a partly working state, so you should try pulling a policy and see what the logs say. I would also install the SCCM Toolkit v2.0 if you haven't already and use Trace32.exe to look at the logs from that directory. You want run a machine policy retrieval and evaluation cycle then look at the policy logs in the c:\windows\system32\ccm\logs directory on a 32-bit machine, or c:\windows\syswow64\ccm\logs on a 64-bit machine.

ahh thanks. I knew it was some place. I forgot all about that new part of vNext. I set my site up yesterday and forgot about this part. I love SCCM but sometimes they over complicate things in the product.

Windows Adv firewall is off by GPO, and there isn't any other firewall on there or AV software. I have another instance on the same box that runs MSDPM and the SSRS on that works fine. Both were configured with Native mode. I reinstalled from scratch yesterday (just default instance, I tried a named one that didn't work either), and pretty much set everything up the same way I did when it was living on the SCCM box, only diff is this is remote and that isn't. I added the computer account, the SSRS report account, and domain admins to every role on the reporting server just to cover my bases. So maybe it is broke when using remote instances or there are some crazy rights that I need to assign it (full rights on SQL and admin rights on the box itself pretty much takes care of everything), it wouldn't surprise me since this is beta 1. I know they said they were working on reworking parts of this component to lessen the hoops you have to go to in order to get it running. I would move the SQL back to the box but when I do the RAM starts pegging 4gigs ish and even with Dynamic memory in Hyper-V the other VMs suffer. So I wanted to run just SQL on my machine with 10gigs of RAM but NOOOO MS has to make you go through hoops with reporting edit: forgot to mention the site is running in Native mode

Where is this box? I found it once, but like everything in SCCM if you don't note where it is and you aren't familiar with installing the role you forget where these small little things are. Anyone help me out here?

When I install the DB role on the primary box running SCCM everything works fine with SSRS. However when I use a remote install of SQL I can never get SSRS working. The connect newsgroups were a waste of time. I keep getting invalid namespace errors. When I go to the SQL box I am able to access the report server and it seems to be working fine, though I have to use the SSL report site because the one on port 80 gives me a 404 error. Everything else is working fine though just this is the only piece not working. I thought it was SQL 2008 SP2 but that wasn't it, so I am thinking that this might be broken in the beta.